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

Annotations already declare destructiveHint=false and readOnlyHint=false; the description goes beyond them by spelling out the user-visible consequences (members see it close, can no longer answer, results freeze) and confirming non-destruction ('Existing responses are kept'). It stops short of covering reversibility or repeated-call/idempotency behavior, which the idempotentHint=false annotation leaves unaddressed.

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?

Three short sentences with the core effect front-loaded and zero redundancy. Every clause carries information: the state change, the member-facing impact, and the data-retention guarantee.

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 single-parameter state-change tool with no output schema, the description covers the effect and data retention well. The remaining gap is that it never says whether the closure is reversible (e.g., via open_project) or what happens if called on an already-closed project.

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?

Only one parameter (project_id) at 100% schema description coverage, so the schema already documents it fully, including its source (list_projects or create_project). The description adds no extra parameter meaning, which is the expected baseline here.

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?

States a specific verb and resource ('Stop a project from accepting new responses') and immediately distinguishes the effect from a delete by noting existing responses are kept and results freeze. An agent can tell this apart from delete_project and open_project without opening any schema.

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 effect is clear, so when to use it is implied, but it never explicitly names the alternative (open_project to reverse, delete_project for removal) or states the condition that selects this over them. Adequate but leaves routing to inference.

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