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

Beyond the annotations (which flag it as a non-read-only, potentially destructive operation), the description discloses that it returns a draft for human review, that it never performs external research or outbound actions, and that a 0.25 USD payment requires explicit wallet authorization. These are significant behavioral details not present in the schema or 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 compact and front-loaded: it opens with the core purpose, then states constraintsstal and pricing. No filler, redundancy, or unnecessary 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 complex tool with five parameters, a nested input object, and no output schema, the description provides important operational context (draft result, cost, payment, no external actions) but leaves out details on the expected shape of the return value and does not compensate for the undocumented schema. Its ambiguity about the deliverable format prevents a higher score.

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 0% description coverage, and the description does not map its terms (brief, source_text, audience, payment_signature, etc.) to input semantics. The only parameter-related hint is that the tool uses buyer-supplied information and mentions the payment requirement, but it doesn't explain the content expected for the required object fields.

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 opens with 'Define metrics with purpose, formula, source requirements, cadence, ownership, and interpretation limits,' naming a concrete verb and a well-specified deliverable. It aligns with the title 'KPI specification' and is clearly distinct from sibling content-generation tools.

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?

It states the tool uses only buyer-supplied information and performs no external research or outbound actions, which sets clear constraints for invocation. However, it does not explicitly list when to prefer this tool over an alternative or provide when-not-to-use guidance, leaving usage to be inferred from the purpose.

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