remove_assumption

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

Details soft-delete behavior, audit trail preservation, impact on linked COs, and inert pointer behavior for controls. With no annotations, description provides substantial transparency about side effects.

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 sentences, each adding value: purpose, deletion effect, restoration hint. No redundant or filler content.

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?

Adequately covers behavior for a soft-delete tool with output schema present. Missing error condition info, but not required given output schema existence.

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 covers 2/3 parameters with descriptions (model_id, assumption_id); server_version lacks description. Description adds no parameter information, achieving baseline for 67% schema coverage.

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?

Clear verb 'soft-delete' with specific resource 'assumption' and mentions side effect of creating a new model version. Distinguishes from siblings like delete_assertion by being specific to assumptions and noting soft-delete behavior.

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?

Implies usage through description of effects, but lacks explicit when-to-use or when-not-to-use guidance. Mentions restoration via restore_assumption, but no direct comparison to alternatives.

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