Strata best bid/ask

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description's 'Read' aligns with these traits and adds 'current' to imply real-time data. No additional context about side effects, rate limits, or error conditions is provided, but none are expected for a simple read.

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?

Single, direct sentence with no unnecessary words. The structure is optimal for conveying the tool's purpose without fluff.

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 simple read operation, the description sufficiently explains what the tool returns (best bid/ask) and its input. It does not elaborate on output structure or error handling, but this is acceptable given the tool's simplicity and lack of an output schema.

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 defines marketId with a pattern, and the description clarifies it is a single 'opaque' market ID, adding meaning beyond the raw pattern. It confirms the parameter's role without guessing its semantic value, which is helpful.

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?

Description clearly states the function: reading the current best bid and ask for a specific market. The term 'top of book' and 'current' specify the exact data type, distinguishing it from broader tools like 'strata_book' or 'strata_quote'.

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 explicit guidance on when to prefer this tool over alternatives. The sibling list includes similar tools like 'strata_book' and 'strata_quote', but the description doesn't mention use cases or scenarios where this BBO endpoint is more appropriate.

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