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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description's 'Read' verb is consistent with that. However, the description adds no further behavioral context, such as whether it returns a combined feed, whether it reflects system-wide or room-specific state, or any pagination or freshness caveats.

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 a single sentence with no wasted words. It front-loads the action ('Read') and then lists the relevant resources in a compact, readable enumeration.

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 input schema and no output schema, the description carries the burden of explaining the tool's result. It names the content areas but does not clarify the shape or aggregation semantics of the response, nor how this tool differs from overlapping list_* siblings. This is adequate but leaves room for agent misinterpretation.

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 there is no parameter information needed in the description. The baseline for zero-parameter tools is 4, and the description adequately communicates the scope of what will be returned.

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 uses the verb 'Read' and enumerates specific governance resources: polls, improvement proposals, compute offers, and steward activity. This is clearer than a tautology, but it doesn't explicitly differentiate itself from sibling tools like list_polls or list_proposals, so it stops short of 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?

There is no guidance on when to use get_governance versus the many sibling tools such as list_polls, list_proposals, or get_steward_state. The description does not state whether this is an aggregated summary, a list view, or something else, leaving the agent to guess the intended use case.

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