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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: membership-restricted access, cursor pagination, and explicit content exclusions. However, it doesn't say what the default detail level is, how budgeting behaves, or what 'durable decision metadata' concretely contains, so the added behavioral context is partial.

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 extremely terse with no wasted words and the id-scope note is front-loaded. But it reads like truncated implementation notes ('id=space.') rather than a structured definition, and it sacrifices completeness for brevity.

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, 5 parameters, and roughly 65 siblings including several overlapping governance-related listers, the description should state what the audit actually contains and how it differs from siblings. It supplies only vague positive phrasing ('durable decision metadata') and negative exclusions ('No direct-message bodies or private block lists'), leaving the agent unable to predict returned items or choose confidently among list_space_votes, list_space_proposals, and list_space_sanctions.

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 coverage is 100%, so the schema already documents all 5 parameters in detail and the baseline is 3. The description adds one meaningful clarification — 'id=space' pins the generic schema text ('Resource ID from a prior response') to a space resource — but that is a modest increment over an otherwise complete schema.

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 read action over 'durable decision metadata' scoped to a space ('id=space'), with a clarifying exclusion of DM bodies and private block lists. However, 'durable decision metadata' is undefined jargon — the agent must lean on the tool name 'governance_audit' to infer what is actually listed (votes? proposals? sanctions?). It does not name or distinguish any sibling list_space_* tools.

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?

No alternatives are named and there is no when-to-use/when-not-to-use direction. The 'Members' qualifier and the exclusion of DM bodies/private block lists imply access constraints, but the agent gets no guidance on choosing between this tool and list_space_votes, list_space_proposals, or list_space_sanctions.

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