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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering safety and idempotency. The description adds context about the baseline being a comparison point, but doesn't disclose additional behavioral traits like overwrite behavior or side effects. 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 with no filler. It front-loads the purpose, includes a clarifying example, and ends with a usage instruction. Every word earns its place.

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?

Given the presence of a full output schema and 100% parameter coverage, the description adequately explains the tool's purpose and usage context. It could mention what happens when called multiple times, but the idempotentHint annotation covers that. The description is complete enough for an agent to invoke correctly.

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 100%, so the baseline score is 3. The description adds value by providing a concrete example ('customer_support_ticket costs $12 per ticket and takes 15 minutes without AI') that maps to process_name, cost_per_unit_usd, unit_label, and avg_duration_minutes, making parameter relationships clearer than the schema alone.

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: 'Define the pre-AI cost baseline for a business process.' It uses a specific verb ('define') and resource ('baseline'), and the example clarifies the exact scope. This distinguishes it from sibling tools focused on ROI calculation or savings reporting.

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 provides clear guidance on when to call: 'Call this once per process to establish the comparison point.' It also explains the baseline's role in subsequent ROI calculations. However, it does not explicitly mention alternatives or when not to use, so a perfect score is not warranted.

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