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

With no annotations provided, the description carries the full behavioral burden. It implies a read-only lookup but never confirms this, nor does it disclose any errors, rate limits, or authentication requirements. The long field list is return-schema content, not behavioral disclosure.

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 dominated by a 17-line dump of output fields rather than a front-loaded purpose statement. This is bloated and poorly structured for an agent trying to determine when and how to call the tool; only the first line provides real signal.

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 simple one-parameter lookup with no output schema, the description should minimally define the parameter and confirm read-only behavior. Instead it lists return fields that belong in an output schema and omits the essential parameter definition and usage context.

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 has 0% description coverage and only one parameter, `istatCode`. The description never explains the expected format, validation, or source of this code — it merely lists returned fields. The parameter's semantics remain entirely unstated in both schema and description.

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 verb 'retrieves detailed data' and the specific resource 'Italian municipality using the ISTAT code.' This distinguishes it from the sibling `find_IT_istat_by_comune_name` (which resolves the reverse lookup) and `find_IT_municipalities_by_zip`, though it doesn't explicitly name those alternatives.

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?

There is no explicit guidance on when to use this tool versus alternatives. The presence of `find_IT_istat_by_comune_name` implies this is the forward lookup when you already have the ISTAT code, but the description never states this condition or any prerequisites.

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