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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine behavioral context beyond that: the temporal windows for each section (72-hour storylines, 30-day publisher coverage) and the fact that a lat/lon resolves to the nearest Mappit place. It does not discuss response shape or limits, but the recency windows are valuable disclosure.

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 with the purpose, then the section inventory, then usage examples and the sibling handoff. The long middle clause is dense but every element maps to a real returned section rather than filler. Slightly heavy for a single sentence, but nothing is wasted.

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?

With no output schema, the description carries the return-value burden and does so by detailing the sections returned and their recency scopes. Annotations cover the safety profile. It stops short of describing ordering, pagination, or the response envelope, which would complete the picture for a read tool.

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 the schema already documents all three params, giving a baseline of 3. The description earns above baseline by enumerating the sections that correspond to the `include` values (about, stories, threads, sources, radio_tv, stocks, conditions) and the overview content behind `detail`. It does not add syntax for `place` beyond what the schema states.

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 resource (a place's profile on Mappit) and enumerates exactly what it returns: overview, latest stories, active storylines, publishers, radio/TV, S&P 500 companies, conditions. It explicitly distinguishes itself from the sibling whats_happening, so an agent can route without inspecting either schema.

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 concrete trigger examples ("tell me about Fort Sumner", "who covers the news in Boise?") and explicitly names the alternative tool and the condition that selects it: for ranked current news use whats_happening. When-to-use and the alternative are both spelled out.

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