azeth_cancel_agreement

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

No annotations provided, so description carries full burden. Discloses critical behavioral traits: immediate effect ('no timelock'), financial consequences ('no penalty', 'not refunded'), authorization rules ('Only the payer'), and exact return value structure ('Transaction hash and final agreement state').

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?

Four sentences with zero waste. Front-loaded with action, followed by usage condition, behavioral warnings, and return specification. Clear logical flow from intent to execution to consequence.

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?

Complete coverage for a 3-parameter destructive operation. Compensates for missing output schema by documenting return values. Covers authorization, side effects, and financial implications necessary for safe blockchain operation invocation.

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 has 100% description coverage establishing baseline 3. Description adds semantic context about ownership ('Only the payer... can cancel') which reinforces the smartAccount parameter constraints, justifying the bump above baseline.

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?

Opens with specific verb+resource ('Cancel an active payment agreement') and explicitly distinguishes from sibling operations like create_payment_agreement or execute_agreement by stating it stops 'recurring payment subscription or data feed' and that 'Only the payer... can cancel'.

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?

Contains explicit 'Use this when:' clause defining the trigger condition (stopping subscriptions/feeds). Also includes prerequisite/authorization constraint ('Only the payer... can cancel') that guides agent away from using this tool for agreements the user doesn't own.

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