Cancel XDaLa session start handoff

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

With no annotations, the description fully bears transparency. It explicitly states what the tool does (cancel metadata) and crucially what it does not do (sign, submit, execute, or cancel on-chain work), providing clear behavioral expectations.

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?

Two sentences efficiently convey the action and its read-only nature. No extraneous information, front-loads the key purpose.

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?

Despite a simple tool with one parameter, the description lacks detail about the 'handle' parameter and does not mention return values or errors. With no output schema, the agent is left without complete context for successful 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?

The schema has 0% description coverage and only a required 'handle' string. The description does not explain what 'handle' refers to, leaving the agent to infer from context. No additional meaning beyond the schema is provided.

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 cancels pending xDaLa session start handoff metadata only, using a specific verb and resource. It distinguishes from sibling tools by emphasizing it is a read-only preparation tool that does not sign or execute on-chain work.

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 implies usage for canceling handoff metadata without on-chain effects, but does not explicitly name alternatives or provide when-not conditions. The read-only nature is highlighted, offering some guidance.

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