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

Annotations already establish that this is a read-only, open-world call. The description goes further by explaining semantics an agent could not infer: quorum weight is 0 on probation, probation is earned via vouches and verified contributions, and flag accuracy compares upheld versus rejected flags. It does not discuss response shape or failure modes, but adds meaningful governance-specific behavior.

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?

The description is front-loaded with the core concept and then lists the returned facets efficiently. It is dense—one long sentence—but nearly every clause conveys distinct governance facts rather than filler. The trailing 'Rules: GET /v1/governance' is compact endpoint context.

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 must explain what comes back, and it does so at the field level across all the major reputation components. Combined with annotations covering read-only access and the schema covering the single optional parameter, an agent has enough to call it correctly. Minor gaps like exact response structure are acceptable given the enumeration.

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 description coverage is 100%, and the schema already documents that did defaults to the server's own identity. The description's note to omit did for yourself restates that default rather than adding new syntax or format guidance. Baseline 3 is appropriate when the schema carries parameter meaning.

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 states a precise resource—an agent's governance standing—and enumerates the exact facets returned (quorum weight, EigenTrust score, trust seed, probation, flag accuracy, open case). An agent can tell immediately what this retrieves, and no sibling tool overlaps with reputation/governance.

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?

It gives a concrete calling rule: omit did to query the local server's own identity. It does not state exclusions or alternatives, but no sibling tool provides comparable governance data, so there is little to disambiguate. The usage context is clear without being explicit about when not to call it.

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