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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds only the return format (GeoJSON FeatureCollection) but does not disclose any behavioral traits beyond what annotations provide. It fails to add significant behavioral context.

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 a single sentence that immediately states the relationship to 'events' and the key differentiator (GeoJSON output). No redundant information; every word adds value.

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?

Given 5 undocumented parameters and no clarification of what 'events' entails, the description is incomplete. While the output schema exists, it does not explain input constraints or behavior. The tool relies heavily on external context.

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?

The input schema has 5 parameters with 0% description coverage, and the tool description provides no information about any parameter. Since schema coverage is low, the description must compensate, but it does not. Users cannot determine how to use parameters without external knowledge (e.g., from the 'events' tool).

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 clearly indicates the tool returns GeoJSON FeatureCollections, distinguishing it from the sibling 'events' tool. It specifies the output format and use case for map rendering, making the purpose clear. However, it relies on knowledge of what 'events' does.

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 explicitly states the tool is 'good for direct map rendering', providing a clear use case. Comparing to 'events' implies that raw events data should be used otherwise. No exclusions or when-not-to-use guidance is given, but the context is sufficient.

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