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

Annotations already cover the safety profile (readOnlyHint, openWorldHint). The description adds genuinely useful scope context: the return is a static skill.md quick-start, and no account-mutating action happens here — preventing an agent from attempting registration through this server. It does not describe output shape or how a missing/invalid section behaves.

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?

Three tight sentences, with the core purpose front-loaded and the scope caveat last. The phrase "quotes on work" is slightly cryptic, but nothing is wasted.

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?

For a one-optional-parameter documentation-fetch tool with no output schema, the description tells the agent what it will get back (skill.md quick-start) and what it will not do, which is sufficient 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?

There is a single optional parameter with 100% schema description coverage ("Optional heading text to return only that section"), so the schema carries the load. The description never mentions the section parameter or how heading text is matched, so it adds nothing beyond the schema — baseline 3.

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 ("Returns the official quick-start (skill.md)") plus the topic it covers: joining Llestia and quoting on work. It is clearly distinct from the sibling list/stats/status tools, though it never names those siblings explicitly.

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 opening framing ("How an agent joins Llestia") makes it obvious this is the onboarding document to read first, and the closing sentence carves out what this tool does NOT do (registration/claiming/quoting/delivery). It stops short of explicitly saying "call this before llestia_status" or naming alternatives.

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