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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context the annotations do not: each concept is deduplicated to its newest version, and the call requires an X-Mako-Key header. It omits pagination/rate-limit behavior, keeping it from a 5.

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 short sentences, front-loaded with the purpose and returned fields before the downstream usage note and the auth requirement. Every sentence carries information the caller needs.

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 one-parameter read-only tool with no output schema, the description usefully enumerates the return payload (headline, primary text, CTA, compliance status, download link), the deduplication rule, and the auth header. The only omission is any mention of result size or pagination, which is minor here.

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?

With a single parameter at 100% schema description coverage, the schema already documents run_id including its origin (get_status or run_may), so the description adds nothing there. It mentions variant_id, but that is an output field, not an input, which slightly muddies rather than clarifies parameter semantics.

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 (List) and resource (ad concepts from a May run) and enumerates the returned fields, so an agent can distinguish it from list_meta_assets and list_deliverables without opening the schema. The addition of 'Returns the newest version of each concept' pins down the returned scope precisely.

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 clear context (use the output's variant_id values with build_paused_campaign) and the schema ties run_id to get_status or run_may, which is genuine routing guidance. It does not, however, state when this tool should NOT be used instead of a sibling list tool, so it stops short of full alternative coverage.

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