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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's 'Read' aligns. The description adds no extra context about potential errors, token validity, or whether the result is cached. The burden is partially covered by annotations, so a 3 is appropriate.

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 sentence that is direct and front-loaded with the verb 'Read'. No wordiness, but the title 'Get ROASTED result' is a stylistic choice that might reduce clarity. Still, the body 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 simple read tool with one parameter and no output schema, the description is adequate. It doesn't specify what the result contains or any prerequisites (e.g., payment), but the sibling names suggest a flow. The description could benefit from mentioning that the token must come from a completed checkout.

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 has only one parameter 'share_token' with minLength 8. The description mentions 'share token' but doesn't add format details or explain the token's role beyond the schema. Since schema coverage is 0%, the description could do more, but the parameter name is self-explanatory.

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 states the verb 'read' and resource 'paid roast result', but the title 'Get ROASTED result' is a stylized variant that may mislead. The purpose is clear enough but lacks specifics about what the result contains.

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 for accessing a paid result via share token, but does not explicitly contrast with siblings like get_roast_offer or prepare_roast_checkout. Agents may need to infer which tool to use based on the context.

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