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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only operation via 'List', and it specifies the output fields. However, it does not explicitly state that it makes no modifications, or mention any performance, paging, or error behavior. The description is adequate but not rich, scoring a 3.

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?

A single, well-structured sentence that front-loads the action and resource, then lists the exact fields returned. No fluff, every word contributes to understanding the tool's purpose.

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 zero-parameter listing tool with no output schema, the description is complete: it tells what is listed and what attributes each item has. It doesn't specify the format or ordering, but that isn't critical for a simple list. It could mention that this is the entry point to obtain a specific guide via get_procedure_guide, but overall it's sufficient.

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 tool has zero parameters, so the baseline is 4. The empty schema means no parameter documentation is needed, and the description doesn't mention any parameters, which is appropriate. Nothing is missing here.

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 states a specific verb ('List') and a specific resource ('step-by-step Spanish procedure guides Expatriator can provide') with explicit output fields (procedure code, name, provinces covered). It clearly differentiates from siblings like get_procedure_guide (which fetches a single guide) and search_immigration_knowledge (which searches broader knowledge).

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 conveys when to use it: to obtain an overview of available procedure guides. While it doesn't explicitly name alternatives or state when not to use it, the zero-parameter nature and the list verb make the context clear. A direct pointer to get_procedure_guide for fetching a specific guide would be an improvement, but the tool's simplicity lowers the need.

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