misp_publish_event

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

Discloses state-changing nature and triggering of alerts. Lacks details on irreversibility or additional side effects, which would be helpful given no annotations.

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?

Two sentences, no fluff, front-loaded with purpose followed by requirement. Every sentence earns its place.

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 purpose and critical condition for a low-complexity tool. Missing explanation of return value or post-publish behavior, but sufficient given context.

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 all parameters; description adds context that confirm is required for destructive action and that publishing triggers alerts, enhancing understandability.

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?

Description clearly states verb 'publish' and resource 'MISP event', with explicit effect 'triggers alerts and notifications'. Distinguishes from sibling tools like misp_create_event or misp_update_event.

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?

Specifies requirement for confirm:true or MISP_ALLOW_DESTRUCTIVE=true, guiding when to use. Not explicit about when not to use, but condition clarifies usage.

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