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

Annotations declare readOnlyHint=true, and the description adds useful behavior beyond that: the endpoint contract, the free/paid distinction, and the x402 Base USDC cost for paid packs. It does not disclose output format or pagination, but the read-only annotation lowers the burden, so this is solid coverage.

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 first sentence states the core purpose, and the subsequent pack lists are compact and directly useful for selecting valid identifiers. The enumeration of packs and costs is slightly long but earns its place since there is no enum in the schema.

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 generic query tool with 8 optional parameters, no required fields, and no output schema, the description should explain that at least one of source_id or pack_id is expected and what the response shape looks like. It relies on the external endpoint contract for that, and while the free/paid pack context is helpful, the missing operational prerequisites leave an agent to guess.

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 the schema already documents each parameter. The description adds value by listing concrete pack IDs, giving example source_id values, and noting cost, which meaningfully enriches the otherwise generic schema descriptions.

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 and resource: 'Generic structured query for direct source_id or pack_id access.' It names the two query targets and ties the behavior to a concrete API contract, distinguishing it from catalog/discovery tools like get_catalog.

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 clearly implies the tool is for querying known source IDs or pack IDs and enumerates which packs are free vs paid. It does not explicitly state when not to use it or mention alternatives like get_catalog or search_disaster_links, so it falls just short of full usage guidance.

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