get_certificate_info

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral caveat that data is not guaranteed real-time, but it does not elaborate on freshness, caching, or other response behavior.

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 compact sentence that front-loads the action and resource, then adds an important caveat without wasted words. Every part earns its place.

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 one-parameter read-only tool with an output schema and strong annotations, the description is nearly complete. The real-time caveat is important and present; the only notable gap is not explicitly routing the agent away from get_certificate_details or toward a real-time alternative.

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 single parameter's schema description already fully explains that order_book_id is the Avanza order-book ID from discovery and not the separate instrumentId. The tool description adds no additional parameter-level detail, so baseline 3 applies given 100% schema coverage.

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 uses a specific verb ('Get') with a clear resource ('certificate identity and latest available market data'). It is clear that this is a certificate-specific info tool and thus distinct from stock/ETF/fund/warrant info tools, though it does not explicitly differentiate from the close sibling get_certificate_details.

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 'latest available market data' implies an appropriate use case, and 'not guaranteed real-time' signals a limitation. However, it does not explicitly state when to use this tool versus get_certificate_details or a real-time quote tool, and it names no alternatives or exclusions.

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