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

Annotations already flag destructiveHint=true, and the description simply says 'removes', adding no new behavioral context. It does not disclose permanence, cascading effects, or any special permissions, which are valuable for a destructive operation.

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 short (six words), which is concise, but the content is largely a restatement of the tool name and adds little informational value. It is not 'appropriately sized' because it under-specifies the operation.

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 destructive delete operation, the description is severely lacking in contextual detail. It does not explain what 'removing an agreement' entails (e.g., irreversibility, associated records, permission requirements), and the available annotations do not compensate for this gap.

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% (though the 'UUID value wrapper' descriptions are minimal), so baseline is 3. The tool description adds no parameter meaning beyond what the schema provides, but the parameter names and types are fairly self-explanatory given the tool name.

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 'DeleteCapTableAgreement removes an agreement' is essentially a tautology of the tool name and title. It states the action verb 'removes' and resource 'agreement' but adds no specificity or differentiation from sibling tools like deleting a round or stakeholder.

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 guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, side effects, or contrast with related cap_table operations, leaving the agent without decision support.

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