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

The annotation readOnlyHint=true already signals a safe read operation. The description adds the contextual detail that the list is 'live' and 'free discovery,' which hints at real-time data and no-cost access, but it does not disclose return format, pagination, or any other behavioral traits. With annotations present, the additional context is minimal, earning a mid-range score.

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, front-loaded sentence that conveys the essential purpose without any fluff. 'Free discovery' immediately sets context, and the rest states the object and scope. Every word earns its place, making it highly concise and well-structured.

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 simple, no-parameter tool with no output schema, the description provides adequate context about what the tool returns (a list of data packs). It lacks details on the return format or how 'live' updates occur, but given the low complexity and read-only annotation, it is sufficiently complete for an agent to understand the tool's role within the sibling set.

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 tool has zero parameters, so the input schema is trivially covered (100%). The description does not need to explain parameters. With no parameters to describe, the baseline score of 4 applies, and the description adds no additional parameter-related semantics.

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 states the tool's function: 'Returns the list of live agent-ready data packs available on DaedalMap.' This uses a specific verb ('returns') and a distinct resource ('data packs'), and the scope ('live agent-ready') differentiates it from sibling tools that focus on disaster links and earthquake events.

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 phrase 'Free discovery' implies this tool is for browsing available data packs, but it does not explicitly state when to use this tool versus alternatives like get_pack or search_disaster_links. No exclusions or alternative recommendations are provided, so usage guidance is only implied.

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