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

With no annotations, the description carries the burden, and it does disclose the return format and provenance (raw markdown, GOVERNANCE.md, dpyc-community repo), which signals a safe, stateless read. It stops short of stating read-only semantics, auth needs, or caching/rate behavior, though for a zero-parameter document fetch those are minor.

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 the document identity and followed by the concrete return payload. No filler and nothing repeated from structured fields.

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 zero-param fetch with an output schema already describing the response shape, the description supplies the essential context: which document and from where. The only gap is that it does not help route between this and the other governance/documentation siblings.

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 is 4; the schema is empty and there is nothing for the description to clarify. No parameter-level ambiguity exists.

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 concrete verb ('Fetch') and a specific resource ('the DPYC Social Contract governance document'), then pins down the artifact (raw markdown of GOVERNANCE.md in dpyc-community). An agent knows exactly what this returns, but nothing distinguishes it from documentation-style siblings like 'about', 'economic_model', or 'how_to_join'.

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?

There is no statement of when to call this versus the many other documentation/spec tools in the sibling list, and no prerequisites or context for retrieving the governance document. The agent must infer usage entirely.

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