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

There are no annotations, so the description carries the full burden of behavioral disclosure. It reveals the read-like nature ('Get') and the returned fields, but omits that this operation uses an npub for credit billing and likely consumes credits; authentication and side-effect details are absent. This is a meaningful gap for a potentially paid operation.

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?

A single tight sentence that front-loads the verb and object and then lists the key attributes. No fluff, no repetition of schema details.

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 single-record get, the description plus the output schema and parameter descriptions cover the basics. However, it lacks explicit guidance on prerequisite steps (browse_catalog) beyond a hint in the blend_id field, and it does not flag the credit-billing side effect. Given the large sibling set, a bit more context would be safer.

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 67%, so the schema already documents blend_id and npub. The tool description adds little about parameters, and it does not explain the dpop_token field or any parameter syntax. This is adequate at the baseline level because the schema mostly handles semantics.

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') and resource ('one coffee blend'), and lists the returned attributes (roast level, decaf status, variants). It clearly indicates a detail lookup rather than a list operation, though it does not explicitly differentiate from siblings like roastify_get_catalog_product or browse_catalog.

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 explicit statement of when to use this tool versus alternatives. The only guidance is implied via the blend_id parameter description, which says the id comes from browse_catalog, suggesting a prior browse step. No when-not or alternative tool is mentioned.

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