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

Annotations declare readOnlyHint and openWorldHint, which are consistent with the description. The description adds behavioral context: paid (1 USDC on Base), generates artifacts (non-destructive), and requires no meeting or account. This goes beyond annotations by revealing the cost and ease of use.

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: first states the purpose and cost, second adds runtime details and condition. Every sentence carries meaning with no wasted words.

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 complex nested schema (3 parameters with deep objects) and absence of an output schema, the description provides a list of generated outputs but does not explain input semantics beyond runtimes. It partially covers what the tool does but leaves gaps in parameter understanding.

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 only 33% (only project_name has a description). The description mentions runtimes ('Cloudflare Agents, Coinbase AgentKit, or an MCP gateway') but does not detail the complex authorization object or its nested fields. As a result, the description insufficiently compensates for the low schema coverage.

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 generates a runtime-specific TypeScript guard, signed action and policy receipt, negative test vectors, and a fail-closed deployment checklist for specific runtimes. The verb 'generates' and resource 'policy pack' are specific, and it distinguishes itself from sibling tools by focusing on policy pack generation.

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 no explicit guidance on when to use this tool versus siblings like intentfence_authorize_action or intentfence_preflight. It only mentions 'No meeting or account is required' as a convenience, but does not clarify use cases or alternatives.

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