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

The readOnlyHint annotation already covers the safety profile, so the description does not need to restate that. It adds the HTTP GET endpoint, which is useful, but offers no additional behavioral context such as response shape, errors, or pagination. This is acceptable for a simple one-parameter read but not rich.

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 extremely concise: two short sentences, with the core action front-loaded and the API route supplied as useful context. Every word 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 single-parameter read-only tool, this is complete: the purpose is stated, the parameter is fully documented in the schema, the read-only annotation is present, and the endpoint is given. Nothing material is missing for correct invocation.

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 fully documents price_id as 'Orb price id.' with 100% coverage. The description adds no extra parameter-level meaning beyond what the schema and endpoint already convey, so the baseline of 3 is appropriate.

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 ('Fetch'), a singular resource ('a single price'), and an identifier ('by id'), making the tool's purpose immediately clear. The API path GET /prices/{price_id} reinforces this and distinguishes it from list-oriented siblings like orb_list_prices.

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 clearly states the context: use this when you need one price by its id. It does not explicitly name alternatives or state when not to use it, but the 'single' qualifier and endpoint provide enough guidance for simple selection.

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