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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and determinism profile needs no restating. The description adds only that the response is 'full structured details', which is a mild hint about return richness already covered by the output schema. No notice of what happens if the slug is unknown.

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?

One sentence, front-loaded with verb and resource, with the lookup key placed at the end. No padding or redundant clauses.

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 a rich output schema, complete annotations, and a fully documented parameter, the description covers enough for correct invocation. A small gap remains around behavior for a missing/invalid slug and the recommended path from search_agencies to this tool.

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% and the single parameter already includes an example ('taycon-ai'). The description merely repeats that the slug is the identifier; per the baseline rule, 3 applies when the schema fully documents the parameter.

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 ('Get') and resource ('full structured details for a specific AI automation agency'), and names the lookup key (slug). It is distinguishable from search_agencies/list_categories by being a single-record fetch, though it never explicitly contrasts with them.

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?

Usage is only implied: 'by its slug identifier' signals a direct lookup once a slug is known, and the presence of search_agencies as a sibling hints at a discovery-then-fetch flow. No explicit when-to-use or when-not-to-use guidance (e.g. use search_agencies first to find the slug) is given.

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