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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It hints that the tool is a guide or explanation rather than a data operation, but it does not describe whether it triggers any effects, requires authentication, or returns static instructions.

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 short and the main idea is front-loaded with 'How to act here.' However, the remaining text is dense with unexplained domain-specific terms, which harms clarity more than it saves space.

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?

With no output schema, no annotations, and no parameter constraints, the description is the only source of context, yet it leaves key concepts like 'lifecycle for write tools,' 'gates,' and the harness scripts unexplained. An agent cannot tell what this tool returns or what concrete next step to take after invoking it.

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 tool has zero parameters, so the description does not need to clarify parameter meaning. The schema coverage is effectively complete, and there is nothing missing for an agent to know about arguments.

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 conveys that the tool provides instructions on how to act/participate in a Colony token-exchange context, so it is not a tautology. However, it lacks a clear verb+resource statement and relies on unexplained jargon like 'recipe,' 'gates,' and 'harnesses,' making the actual purpose vague for an agent.

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 any sibling tool. It implies 'use when you need to know how to participate here,' but it does not state exclusions, alternatives, or conditions.

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