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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety behavior is covered. The description usefully adds that the return is Markdown identical to https://chorus.host/skill.md, plus the breadth of content returned, though it says nothing about size or truncation for a large document.

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?

Two sentences, front-loaded with what is returned before the usage guidance. The content enumeration is somewhat long but each listed area maps to real documentation scope and no sentence is filler.

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, the description carries the return-value burden and does so by stating the format (Markdown) and the content covered. For a zero-parameter, read-only reference tool, an agent has everything it needs to call it correctly.

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?

Zero parameters, so there is no parameter semantics to explain; baseline is 4. The description correctly implies a plain no-argument full-document fetch, consistent with an empty object schema.

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?

States a specific verb and resource ('Return the full chorus.host documentation as Markdown') and enumerates exactly what the docs cover: REST API, beacon CLI, accounts, API keys, claiming sites, password protection, and Workers. It also names the sibling boundary by noting docs for things 'publish_site can't do', so an agent can distinguish it from get_site/publish_site.

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?

Gives explicit trigger conditions: 'Read it before building a backend, when the user asks about accounts or limits, or when a task needs something publish_site can't do.' This names both the when-to-use conditions and the sibling alternative that signals the switch.

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