Get price

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond 'retrieves' – no error behavior for unknown IDs, no note about access scoping via the account parameter, no context on what a 'price' object represents.

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?

One short sentence, front-loaded with the verb and resource. It is not padded or redundant, though at this length it barely qualifies as a description at all.

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 3-parameter, open-world, read-only lookup with no output schema, the description leaves the return shape, the meaning of the account scoping parameter, and the include expansion semantics entirely to the schema. An agent can call it, but cannot anticipate the response or the cross-account behavior.

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 100%, so the schema already documents id, account and include with real constraints (pattern, maxLength, relationship list). The description names only 'the given ID' and ignores the account and include parameters entirely, adding no value over the schema. Baseline 3 applies when the schema carries the load.

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?

States a specific verb (retrieves) and resource (price) keyed by ID, which is clear enough to identify the operation. However, it does nothing to distinguish get_price from its sibling list_prices, and 'the price' adds no scope or context beyond the name.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives like list_prices for enumeration. The agent gets no routing signal beyond the naming convention shared across the entire get_* family.

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