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

No annotations are provided, so the description must fully disclose behavior. It fails to state that this is a read-only, informational tool with no side effects. The mention of 'write tools' could mislead an agent into thinking this tool performs writes or requires write context.

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 minimal (single sentence) but packs domain-specific terms without explanation, reducing clarity for an agent. It is moderately concise but sacrifices understandability.

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 trivial empty schema and no output schema, the description is incomplete for a documentation tool: it does not specify output format (text, JSON?), nor explain its cryptic terms. An agent cannot fully anticipate what this tool returns or how to process 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?

With zero parameters and 100% schema coverage, the description does not need to add parameter meaning. The absence of param info is acceptable, so the baseline score of 4 applies.

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 is vague and jargon-heavy ('Colony token-exchange recipe', 'lifecycle', 'gates', 'harnesses'), lacking an explicit verb or outcome. It does not clearly state that the tool returns instructional documentation, leaving its purpose ambiguous despite the suggestive name.

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 guidance on when to use this tool versus the many sibling tools (e.g., propose, vote, submit_measurement). The description does not clarify that this is a reference/documentation tool rather than an action tool, nor does it provide exclusions or alternatives.

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