Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful scope context beyond that: results are limited to the caller's own saved themes, and the payload includes colours, fonts, logo and social links. It does not describe list ordering or whether ids are returned per item, which are the remaining behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each doing distinct work: define the resource and its contents, disambiguate from the nearest sibling, then describe the trigger and the downstream use. The most important discriminator (user's identity vs. built-in presets) is front-loaded and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with full annotation coverage and no output schema, the description covers what is returned conceptually, when to call it, and how to consume the result. The only shortfall is that it doesn't sketch the shape of the returned list (e.g., whether name/id/colour values are included), which the agent must infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4. The description correctly implies an unfiltered listing with no arguments, and the mention of 'caller's own' clarifies that scoping comes from auth rather than an input field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list the caller's saved Brand Themes) and immediately enumerates what one contains: colours, fonts, logo, social links. It explicitly distinguishes itself from the sibling get_design_options by contrasting user-owned themes with Unplain's built-in presets, so an agent can route correctly without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete trigger phrases ('my brand', 'our colours', naming their company) and names the alternative (get_design_options) with the condition that selects it. It also closes the loop by explaining the follow-up action: pass the theme's id as brandThemeId to create_ebook or update_ebook.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.