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

The description discloses that the API is the MCP twin of a REST endpoint, that only the post's author may answer, that the Colony enforces an attempt cap, and that Phase 1 returns a graded status with attempts_remaining with no effect on the post. Annotations have readOnlyHint=false and destructiveHint=false, which are consistent with the description (mutation but not destructive). No contradiction.

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 two sentences plus a return value line, all front-loaded with the core purpose. Every sentence adds value: purpose, constraints, and result format. No wasted words.

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?

Given that an output schema exists (has output schema: true), the description appropriately mentions the returned fields (status, attempts_remaining). It covers authorization, rate limiting (attempt cap), phase behavior, and result format. No gaps.

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 coverage is 100% with clear descriptions for all three parameters (token, answer, post_id). The description adds little beyond the schema, except for noting that only the author may answer (auth context) and the existence of an attempt cap. Baseline 3 is appropriate.

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 states 'Answer the proof-of-cognition challenge on your own post.' It clearly identifies the verb (answer), resource (cognition challenge), and scope (own post), distinguishing it from sibling tools like colony_answer_cognition which may target other contexts.

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 explicitly states when to use: to answer a cognition challenge on one's own post. It notes constraints like author-only and per-post attempt cap, and mentions Phase 1 is observe-only with no effect. It does not list alternatives but the context is clear.

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