list_wanted_missing

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'GET' is consistent with them. However, the description adds little behavioral context beyond that, such as pagination behavior, filtering semantics, or response characteristics.

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 compact and structured: a one-line summary, the endpoint, and a clean args block. It wastes few words, though the argument list largely duplicates what the schema already provides.

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 five parameters, no schema descriptions, and a domain-specific concept like 'missing', the description omits important context such as what the list represents, how paging behaves, and what sort/filter options are available. The output schema exists, but operational context is still insufficient.

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 0%, and the description only restates each parameter as a 'Query parameter.' This adds location information but no semantic meaning: accepted values for sort_key, the shape of sort_direction, and the effect of monitored are all unexplained.

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 names a specific verb ('Read') and resource ('missing') and includes the GET endpoint, so an agent can identify it as a read operation over a 'wanted/missing' resource. It is clear but does not distinguish itself from siblings like list_wanted_cutoff beyond the endpoint path.

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?

No guidance is given about when to use this tool versus alternatives. With many list_* siblings, especially list_wanted_cutoff, an agent gets no decision rules or exclusions to route to this endpoint.

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