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

With readOnlyHint=true already in annotations, the safety profile is covered. The description adds a valuable behavioral fact: the tool returns null when the project has no radar snapshot, which is essential for handling the response. It also notes the per-topic suggestion counts, enriching the agent's understanding of the result beyond the annotation.

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?

Two sentences, no filler. The core action and resource are front-loaded, the return contents and null edge case are in the first sentence, and the alternative usage occupies the second. Every clause earns its place.

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 single-parameter read operation, the description gives a thorough picture of the return value (topic fields, index, suggestion counts) and the null case, while directing to the next step via expand_radar_topic. With no output schema, this is largely sufficient; only minor details like ordering or pagination are absent, which are low-impact for a snapshot listing.

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 schema has 0% description coverage for projectId, and the description only mentions 'for a project' in passing. It does not explicitly confirm that projectId is the unique identifier for the target project or explain any value format. With zero schema coverage, the description should take on the burden of parameter explanation, and it falls short.

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 opens with a specific verb ('List') and a concrete resource ('the latest emergent-topic radar snapshot for a project'), then enumerates the exact contents (label, summary, momentum, novelty, drivers, evidence, per-topic index, suggestion counts). It explicitly contrasts itself with expand_radar_topic, so there is no ambiguity about what this tool does or how it differs from its closest sibling.

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 directs the agent to use expand_radar_topic when the goal is to turn a topic into article angles, giving a clear alternative and the condition that triggers it. It also implies this tool is the listing step. It does not enumerate all exclusions, but the named sibling provides strong routing context.

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