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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds that events are upcoming and filterable, which is useful but does not disclose rate limits, pagination, auth requirements, or response structure. With annotations present, this is adequate but not rich.

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?

Single sentence, twelve words, front-loaded with the action and resource. No unnecessary words.

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 read-only listing tool with four optional parameters and no output schema, the description covers the core purpose and two filter dimensions but omits the limit parameter and any indication of pagination or response format. It is adequate for basic invocation but leaves some exploration to the agent.

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 50% (date and lang have descriptions; city and limit do not). The description adds filter semantics for city and date, partially compensating, but limit remains undocumented outside the schema, and lang's behavior is only in the schema. It adds some meaning beyond schema but not complete.

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 ('List'), resource ('upcoming Pionra events'), and optional filters ('by city and date'). This clearly distinguishes it from siblings like find_housing, find_jobs, and search_pionra, which target different resources.

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?

The description implies the tool is for retrieving upcoming events, but it does not explicitly state when to prefer it over search_pionra or other siblings, nor does it mention any exclusions. The use case is clear from the resource named, but no alternatives or conditions are given.

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