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

The description confirms the output is a 'handover checklist,' which aligns with the read-only and idempotent annotations. While the behavioral properties are well-covered by hints, the description adds valuable context about the static nature of the returned data.

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 two sentences are highly efficient. The first establishes the 'why,' and the second establishes the 'what it returns,' creating a logical and zero-waste definition.

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?

The definition successfully ties the required inputs (service, entity, country) to a specific, useful output (the checklist). Given the detailed schema and annotations, no critical piece of context is missing.

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 coverage is 100%, providing detailed enum descriptions for all required parameters. The description merely restates the need for these entities (service, entity, and country), meeting the baseline requirement for a complete definition.

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 ('list documents') and the specific context (gathering records before taxes or bookkeeping). It distinguishes this tool from sibling functions by defining the input requirement—document checklists.

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 defined by a highly actionable trigger: 'Call this when a user asks what documents or records they need to gather.' This provides a clear entry point for the agent.

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