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

The readOnlyHint=true annotation already establishes this as a safe read, so the bar is lower. The description usefully discloses what is returned (vote counts, council responses), but says nothing about pagination, ordering, or default window behavior despite the presence of 'da' and 'limite' parameters.

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-formed sentence with the verb and resource front-loaded and no wasted wording. It is appropriately sized, though arguably too terse for the pagination parameters it exposes.

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 low-complexity list tool with no output schema and no nested objects, the description covers the core purpose. However, with two undocumented pagination parameters and no return-shape hints beyond the field list, it is only minimally complete.

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 description coverage is 0% and the description never references the two parameters. 'da' (offset/from) and 'limite' (limit up to 200) are left entirely undocumented, so the description does not compensate for the schema gap.

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 ('Elenca') and a specific resource ('istanze consultive del municipio'), plus the payload it returns (vote counts and council responses). It is clear what the tool does, though it does not explicitly distinguish itself from sibling list/read tools like leggi_registro or cerca_archivio.

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 when-to-use guidance, no mention of the read counterpart of proponi_istanza, and no exclusions versus other 'leggi_*' siblings. The agent must infer usage entirely from the resource name.

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