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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds valuable behavioral context: it explicitly says the tool returns checklist data 'without rendering a widget' (so no UI side effects) and instructs to 'preserve the research disclosure in any explanation', which is a specific behavior not covered by annotations.

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 two concise sentences with no filler. It front-loads the primary purpose and adds one critical behavioral instruction. Every word earns its place.

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 the presence of an output schema (rendering return value explanation unnecessary) and detailed parameter descriptions, the description is nearly complete. It could briefly note that the 'applicants' parameter is optional for personalizing requirements, but overall it provides sufficient context for an AI agent.

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 coverage is 100%, with detailed descriptions for all 4 parameters (language, officeId, applicants, procedureId). The description does not provide additional meaning beyond what the schema already communicates, so a baseline score of 3 is appropriate.

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 tool returns 'concise, office-aware checklist data for one consular procedure' without rendering a widget, distinguishing it from sibling tools like search_consular_procedures (which returns a list) and show_consular_dossier (which likely shows a dossier). The verb 'Return' and resource 'checklist data' are specific.

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 context is implied (to retrieve details for a specific procedure after using search_consular_procedures), but there is no explicit guidance on when not to use it or mention of alternatives. The description could be improved by noting that it is for individual procedures, not for browsing.

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