guild_get_prune_count

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

The description explains the non-obvious prune role semantics (ALL roles must be listed, no-role members always pruned) and clarifies that this is a preview returning an estimate, not an actual prune. This adds behavioral context beyond the read-only/idempotent annotations without contradicting them.

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 well-structured with bold headers (Purpose, When to use, etc.), front-loaded with the key purpose, and every sentence earns its place. It is compact yet thorough without redundancy.

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?

Given the tool's simplicity, the presence of an output schema, and strong annotations, the description covers purpose, usage, parameter semantics, and return value. No significant gaps remain; it is fully self-contained for an agent to invoke correctly.

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%, so the parameters are already documented. The description repeats the include_roles logic verbatim from the schema and does not add new parameter meaning, though it does clearly reference the return value. Baseline 3 is appropriate.

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 specific verb 'Preview' and names the exact resource ('how many members would be pruned'), clearly distinguishing this from sibling tools like guild_begin_prune. It states the tool's purpose succinctly and unambiguously.

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?

Explicitly tells the agent when to use it: 'Estimate impact before calling guild_begin_prune', naming the relevant sibling tool. It also clarifies the nuanced behavior of include_roles, which helps avoid incorrect use.

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