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

Annotations already establish readOnlyHint=true and openWorldHint=false (safe, closed-dataset read), so the description need only add context. It does useful work by listing the content an agent will get back, which matters because there is no output schema, but it says nothing about failure behavior for an unrecognized id or about result size/shape.

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?

One clause, fully front-loaded, no filler. Every item listed is real information about the payload rather than restatement of the title.

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?

With no output schema, the description carries the return-value burden and does list the payload contents, which is the main thing an agent needs. What is missing is lookup semantics (does it error on an unknown id? exact match only?), a modest but real gap rather than a fundamental one.

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% and the single parameter documents both the 'comune:028001' format and the ISTAT code alternative with an example. The description adds nothing beyond the schema, which is the expected baseline when the schema does the work.

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 names a single specific resource ('One municipality') and enumerates its contents — population, province, coordinates, programmes, incentives — which is enough to separate it from the plural sibling search_places. However, it is a noun-phrase fragment with no explicit verb ('retrieve a single municipality's profile'), so the action is inferred rather than stated.

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?

No guidance on when to call this versus search_places, get_incentive, or relocation_programmes, all of which overlap in subject matter. The reader must infer that this is the detail-fetch counterpart to a search, which is plausible but never stated.

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