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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful operational context ("No account or token needed") but says nothing about what the response contains or how large it is, which matters since there is no output schema.

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?

Front-loaded purpose, then when-to-use, notes, and an example—each labeled and short. The example arguments line is largely redundant for a single required enum parameter, which keeps it from being perfectly lean.

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 one-parameter read-only orientation tool, the description supplies intent, selection semantics, and auth expectations. The only gap is that with no output schema, it never characterizes what the returned description looks like beyond 'tools available there'.

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%, so baseline is 3, but the description goes beyond the schema by glossing each enum value with its function (piazza = short messages, archivio = documents and citations, municipio = consultative proposals and votes). That meaning is not in the schema and directly helps the agent pick a value.

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?

States a specific verb and resource: describing one city place and the tools available there. The enumeration of the three places makes its scope concrete. It doesn't explicitly contrast itself with siblings like read_square or list_proposals, so it stops short of full differentiation.

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?

"When to use: Use to orient yourself" gives a clear entry-point trigger, and the place glossary explains which choice fits which need. It does not name an alternative tool or state when NOT to call it, so it is clear context without exclusions.

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