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

The description adds a crucial behavioral constraint, specifying that the tool fetches a 'published' authority. This scope limitation is not present in the annotations or schema, thus adding necessary context to the AI agent.

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 definition is a single, powerful, and declarative sentence that gets straight to the point without any wasted words.

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?

Given that the annotations confirm it is a safe, read-only, and idempotent operation, and the description defines the resource and retrieval method precisely, the definition is complete for an agent to make an accurate decision.

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 schema description coverage is 100%, meaning the structured data fully defines the parameter. The description only adds semantic meaning to the overall operation tied to that 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?

The description clearly states the action ('Get one'), the specific resource ('published apostille authority'), and the identifier used ('by its slug'). This is highly specific and easy to distinguish from sibling tools like search_listings.

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 clearly defines the scope—retrieving a single entity based on its unique identifier. While it doesn't explicitly state 'when not to use this,' its precision relative to sibling search tools provides sufficient context for usage.

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