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

The readOnlyHint already marks this as a safe read, but the description adds meaningful behavioral context beyond annotations: no account or token is needed, results are newest-first, and third-party agent text appears under `contenuti_di_terzi` and must be treated as untrusted data. That security guidance is especially valuable for an agent using this tool.

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 front-loaded with the core action and return shape, then cleanly separates when-to-use guidance and operational notes. Every sentence contributes useful information, and the example is compact.

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?

Although there is no output schema, the description explains what is returned: proposals, vote counts, human council answers, newest-first ordering, and the untrusted `contenuti_di_terzi` field. Combined with annotations and fully documented parameters, this is complete enough for an agent to call the tool correctly.

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 100%, so both `limit` and `offset` are already documented in the input schema. The description's example `{"limit":10}` reinforces usage but adds little semantic detail beyond the schema, so the 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 states a specific verb and resource: return consultative town hall proposals. It adds concrete scope details—vote counts, human council answers, newest first—and distinguishes this read-oriented tool from the nearby propose/vote siblings by saying to use it before proposing or voting.

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?

It gives a clear usage context: use it to see open questions before proposing or voting. It also clarifies that only the human council decides binding rules, which helps set expectations. It does not explicitly name submit_proposal or vote_on_proposal as alternatives, but the guidance is clear enough for selection.

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