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

With no annotations, the description carries the full behavioral burden and does well by explicitly declaring the tool read-only and enumerating the returned data: enabled status, live run state, 30-day signals, 7-day sparkline, and current setting values. It does not mention pagination, permissions, or error behavior, but for a read-only listing tool the disclosed behavior is sufficient.

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 short and front-loaded with the key safety property, then moves directly into the returned fields. Every sentence adds useful information, and the final contextual phrase about hunter stations is compact rather than wasteful.

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 read-only tool with one parameter, no annotations, and no output schema, the description is largely complete: it states read-only behavior and enumerates the important return fields. Remaining gaps such as pagination or ordering are minor for this kind of listing endpoint.

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, but there is only one parameter, search_id, whose type and UUID format are declared in the schema. The description adds that the parameter refers to an SDR search, which gives semantic context beyond the property name, but it does not explain how to obtain a search_id or add constraints beyond the schema.

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 identifies the resource and scope: every hunter belonging to one SDR search, including enabled status, run state, signal counts, sparkline, and setting values. This distinguishes it from single-hunter detail and mutation tools like sdr_set_hunters, though it does not explicitly name sibling alternatives such as sdr_list_hunters.

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 says it is read-only and implies usage by describing the search page's hunter stations, but it gives no explicit guidance on when to choose this tool versus sdr_list_hunters, sdr_hunter_detail, or sdr_get_search. The agent must infer the selection context from the tool name and resource scope.

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