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

The description states 'no external research or outbound actions' but annotations include openWorldHint=true, which implies the tool may access external data. This is a direct contradiction. Additionally, destructiveHint=true is not addressed but the description does mention payment and wallet authorization, which is helpful. The contradiction forces a score of 1.

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 concise (two sentences) and front-loads the primary purpose. It includes pricing and payment details, which are relevant for agent decision-making. However, it crams multiple pieces of info (purpose, constraints, output, price) into one sentence, slightly harming readability.

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?

The tool has nested objects, no output schema, and 0% parameter coverage. The description does not explain the return format beyond 'a draft,' nor does it address the significance of fields like idempotency_key or payment_signature. The contradiction with annotations further undermines completeness.

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%, and the description provides no explanation of the parameters (brief, source_text, audience, etc.). It only vaguely references 'supplied instructions,' which does not compensate for the lack of parameter documentation. For a nested object schema with 5 parameters, this is a significant gap.

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 action ('Write a task-specific SOP') and the resource ('SOP') with content components (prerequisites, steps, verification, escalation points). It is specific enough to distinguish from generic writing tools, though it does not explicitly differentiate from similar siblings like process_document or project_plan, so it loses a point.

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 gives context that it uses only buyer-supplied information and returns a draft for human review, implying when to use it. However, it does not state explicit when-not-to-use conditions or mention alternatives, leaving the agent to infer the scope.

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