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

The description states '(READ-ONLY: mutations refused)', but annotations declare readOnlyHint=false, directly contradicting the claim. The description also mentions executing Action Skeleton cycles and transmitting packets, but the read-only contradiction is a serious inconsistency.

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 only two sentences and front-loads the core action, which is structurally sound. However, the dense jargon and contradictory read-only note reduce clarity, and some phrases do not earn their place for an agent trying to invoke the tool correctly.

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 an 8-parameter execution tool with no output schema, the description is incomplete: it does not explain side effects, return values, or the interaction between execute, dry_run, and strict. The annotation contradiction further undermines completeness, leaving the agent with insufficient behavioral context.

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 input schema already documents all 8 parameters in detail. The description adds only marginal meaning, such as 'transmits swarm mudra packet to P2P peer' for the peer parameter, but does not clarify execute vs. dry_run or strict semantics beyond what the schema already says.

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 provides a specific verb+resource ('Evaluate and dispatch a ... Sutra Codon') and explains mechanics like precondition validation and execution. However, the purpose is obscured by heavy jargon ('Kekkai sandbox boundaries', 'Action Skeleton cycles', 'swarm mudra packet') and it does not differentiate from siblings such as sutra.compile or sutra.route.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor on when not to use it. The only conditional cue is the contradictory '(READ-ONLY: mutations refused)' parenthetical, which does not help an agent choose between this and other sutra.* tools.

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