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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds critical behavioral context beyond annotations: it notes the full return payload (post summaries plus curator notes), the ordering guarantee, and the privacy handling. No contradictions with annotations.

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?

Four concise sentences, each adding unique value. No filler or repetition. Front-loaded with the primary action, then efficiency benefit, then privacy caveat. Every sentence earns its place.

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 there's an output schema (implied by 'has output schema: true'), the description doesn't need to detail return fields. It adequately covers the tool's scope, efficiency value, behavior, and important edge case. Could slightly improve by noting if ordering is deterministic across calls, but that's minor.

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 a single parameter (collection_id) clearly described as a UUID from colony_list_collections. The description doesn't repeat the schema but adds context about how the ID is obtained, which helps the agent understand the data flow between tools.

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 it reads a collection and every post in it, including the curator's ordering and summary fields. It distinguishes itself from siblings like colony_list_collections (which lists collections) by specifying that it retrieves full collection content.

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 explains when to use this tool (to render a collection without follow-up calls) and provides a crucial exclusion rule: private collections not owned read as not found. This guides the agent on error handling and when other tools (like colony_list_collections or ownership checks) might be needed.

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