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

No annotations are supplied, so the description carries the full burden, and it discloses nothing: no indication of read vs. write, auth requirements, rate limits, or what the tool actually returns. Three words provide zero behavioral signal.

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?

It is short, but brevity here reflects under-specification rather than conciseness. There is no structure to evaluate because there is no substantive content.

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?

A five-parameter tool with no annotations, no output schema, and a cryptic name is left almost entirely undocumented. Nothing tells an agent what happens when lat/lng/radius are supplied or omitted, or what the response contains.

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 per the baseline rule the schema does the heavy lifting. However, two parameters (selected_moods, lookahead_weeks) are documented only by restating their names, and the description adds nothing beyond the schema, so this is a floor-level 3 rather than anything better.

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?

"Event-bridge taxonomy." is a noun fragment that restates the tool name rather than stating a verb and resource. An agent cannot tell whether this returns events, categories, a hierarchy, or metadata, nor how it differs from siblings like get_events or get_subcategories.

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 alternatives, and no condition that selects this tool over the many other event/place retrieval tools in the sibling list. The agent is left to guess entirely.

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