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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description reinforces this by stating it does not spend credits or authorize purchases, which adds little beyond the annotations. The only new behavioral detail is the artifact_ids requirement for context-pack quotes, which is a parameter constraint rather than a behavioral trait. No contradiction with 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 two sentences, front-loaded with the core purpose and safety guarantee. It is efficient and free of fluff. Minor loss for not structuring the artifact_ids note more clearly, but overall it is concise.

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 quote tool with no output schema, the description should explain what the tool returns (e.g., price in credits) and how the operation parameter affects the quote. It does neither. The artifact_ids requirement is a start, but the description is incomplete for an agent to invoke the tool correctly across all operation types.

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%, so the description must compensate for parameter meaning. It only mentions that context-pack quotes require artifact_ids, leaving input_bytes, ttl_seconds, artifact_id, and the operation enum unexplained. This is insufficient for an agent to correctly construct a quote request, especially with 5 parameters and a required enum.

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 clearly states the tool's purpose: to inspect the service-credit price before execution. It also clarifies it does not spend credits or authorize purchases, which distinguishes it from payment/execution tools. However, it does not explicitly name sibling alternatives, so it lacks the explicit differentiation seen in top-tier definitions.

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 'before execution' and notes that context-pack quotes require artifact_ids, which is a concrete prerequisite. It does not explicitly state when not to use the tool or name alternative tools (e.g., mithrandir_pricing). The guidance is present but not comprehensive.

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