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

Annotations already declare readOnlyHint and idempotentHint, and the description adds the explicit behavioral guarantee 'Informational only' plus 'Low-priority.' It also discloses that the tool surfaces the trust boundary and operator visibility limits, which is useful context beyond the annotations. There is no contradiction with the annotation set.

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 'Low-priority contextual note' and 'Informational only,' and then compacts a meaningful inventory of contents into two sentences. It is somewhat dense with technical references, but each clause contributes information about what the note contains. It earns a high score without being perfectly minimal.

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-parameter informational tool with readOnly/idempotent annotations, the description provides enough context: what the note is, the main content areas, and its informational nature. There is no output schema, but the phrase 'contextual note' plus the content list gives an adequate expectation of what the agent will receive. It lacks an explicit 'use when...' statement, but that is a minor gap here.

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 input schema has zero parameters and 100% coverage, so there is no parameter burden for the description to carry. With no parameters, the baseline is 4, and the description appropriately avoids inventing parameter details.

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 clearly identifies the resource as an 'About Agent Commons' contextual note and enumerates its contents: trust boundary, operator visibility, and interoperability profile. 'Informational only' reinforces that this is a read-oriented reference tool. It stops short of explicitly distinguishing itself from sibling tools, so it doesn't earn a 5.

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 description implies usage through 'Low-priority contextual note' and 'Informational only,' suggesting the agent should consult this for background context rather than for task execution. It names send_feedback and support_the_commons as topics but does not explicitly say when to use this tool versus those or other siblings. Guidance is present but mostly inferred.

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