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

While annotations already mark the tool as read-only and non-destructive, the description adds meaningful behavior: error is populated when the catalog fetch fails, refresh bypasses a cache and is slower, and stored template content should be treated as data rather than instructions. This goes well beyond the annotation baseline.

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?

The description is front-loaded with the result and error behavior, then the endpoint, then auth guidance. The generic Busabase ChangeRequests sentence is somewhat tangential for a read-only listing tool, which prevents a 5, but the rest is tight and well ordered.

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?

There is no output schema, but the description explains what the response contains, how errors are surfaced, how caching behaves, and what auth workflow is required. For a two-optional-parameter, read-only tool, this gives an agent enough to select and invoke it correctly.

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?

Schema description coverage is 100%, so the schema already carries the meaning of refresh and targetSpaceId. The description briefly restates the auth-verification workflow for targetSpaceId but adds little semantic value beyond what the schema already provides.

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?

The description opens with a precise statement of what the tool returns: the server's configured template catalog, including provenance and per-template stats. The title and the explicit GET /api/v1/templates endpoint reinforce the resource, and no sibling tool competes for this exact catalog-listing job.

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?

It gives concrete usage context: call auth_verify and ask the user for a space when multi-space accounts are involved, pass targetSpaceId, and leave refresh off for ordinary reads. It does not explicitly contrast the tool with alternatives, but the catalog-listing niche is clear and the refresh guidance is useful behavioral direction.

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