filter_certificates

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

With annotations already declaring readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, the description adds useful context beyond annotations: server-side pagination, upstream-defined filter labels, and the need to extract orderbookId from results. No contradiction exists between the description and annotations.

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 three short sentences with the core purpose front-loaded. Each sentence earns its place: core action, open-world filter labels, and the critical downstream orderbookId step.

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, idempotent filter tool with an output schema, the description covers the key non-obvious behavioral details: open filter vocabulary, pagination, and using orderbookId before info/detail calls. It does not fully discuss filter combination semantics, but the schema defaults and output schema cover much of that burden.

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 does not explain any of the 10 parameters or map concepts like 'leverages' or 'underlying_instruments' to the orderbookId hint. The generic warning that filter labels are upstream-defined helps but does not compensate for the lack of parameter-level documentation.

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: 'Select certificates by upstream filters with server-side pagination.' This clearly identifies it as a filtered list operation for certificates, but it does not explicitly differentiate it from similar siblings like filter_etfs or filter_warrants.

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 implies usage context by instructing the agent to 'Select an orderbookId from results before requesting info or extended details,' which positions this tool as a discovery step before certificate info/detail calls. However, it does not explicitly say when to use this over filter_etfs/filter_warrants or state any exclusions.

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