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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no extra behavioral context such as pagination behavior, default ordering, or whether deleted templates can be included. Since the annotations are strong, a neutral description earns a baseline 3; no contradiction exists.

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 a single sentence with no unnecessary words. It is front-loaded and immediately states the action and resource. There is no wasted content, making it optimally concise.

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?

With no output schema, the description should help the agent understand what the response looks like, but it does not. It also omits pagination details (limit/offset) and the option to include deleted templates, both of which are part of the tool's behavior. While annotations clarify safety, the description lacks enough information about usage nuances and expected return shape for a complete picture.

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 only 33% (only includeDeleted has a description). The tool description does not compensate for the missing descriptions of limit and offset, nor does it mention pagination or the includeDeleted option. It adds no meaning beyond the schema fields, which are already sparse. The agent must infer the semantics of limit/offset from defaults and ranges alone.

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 'List enrichment templates' uses a specific verb ('List') and a clear resource ('enrichment templates'), making the primary purpose obvious. It distinguishes from sibling CRUD operations like enrichment_templates-get (which implies fetching a single item) and create/update/delete. However, it does not explicitly mention pagination or filtering, but the verb and resource are clear enough.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is for listing all templates, or when to use enrichment_templates-get for a specific template, or how it differs from enrichment_types-list. No exclusions or alternatives are stated, so the agent is left without decision-support information.

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