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

With no annotations present, the description carries the full burden and does well: it discloses the exact content of the payload (eight named steps) and its provenance ('fetched live from docs/how-to-add-authority.md in the dpyc-community repo'), which tells the agent the content is current and read-only. It stops short of stating auth requirements or whether the fetch can fail/rate-limit.

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?

Purpose is front-loaded in the first sentence, with supporting detail in the second. The step enumeration is long but each item helps an agent decide whether this guide covers its need, so it earns its space.

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 no-argument guide tool with an output schema, the description is sufficient: it tells the agent what the document contains and where it comes from, so return-format details can safely live in the output schema. Nothing an agent needs to call it correctly is missing.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. No parameter text is needed or missing.

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 deliverable: an end-to-end eight-step guide for spinning up a new Tollbooth Authority, plus an itemized preview of what the guide covers. It is clearly a documentation-lookup tool rather than an action tool, but it never names its closest siblings (register_authority, how_to_join) to draw the line 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?

Usage is only implied: an agent can infer this is the pre-flight reading material before calling register_authority, but the description never says when to consult it versus performing the registration itself. No prerequisites, no exclusions, no named alternative.

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