misp_delete_attribute

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

Discloses destructive nature and requirements for confirm and confirmHard. However, without annotations, it fails to describe side effects, soft delete recoverability, or permission needs beyond flags.

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?

Single sentence with essential info, front-loaded. Could be slightly clearer but efficiently conveys purpose and key constraints.

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?

Adequate for a delete operation with 4 params and no output schema. Lacks return value description, error handling, and deeper behavioral details.

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 baseline is 3. The description adds minimal extra value over the schema's parameter descriptions; it reiterates confirm and confirmHard requirements.

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 clearly states the tool deletes an attribute from MISP, specifying soft or hard deletion. This differentiates it from siblings like misp_delete_event and misp_delete_object.

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 on when to use this tool versus alternatives like misp_delete_object or misp_delete_event. Lacks context for soft vs hard delete selection or prerequisites.

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