misp_export_iocs

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

No annotations are provided, so the description carries the full burden. It states 'Export IOCs' but does not disclose whether the export returns a file, a blob, or a URL, nor does it mention authentication requirements or side effects. The tool likely performs a read operation, but this is not confirmed.

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 a single sentence that is concise and front-loaded with the main action. It contains no wasted words, though it could be slightly more informative about behavior. It is appropriately sized for a simple export tool.

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?

Given the tool has 5 parameters and no output schema or annotations, the description is incomplete. It does not explain what the output looks like (e.g., file download, JSON, text stream) or how the filtering parameters interact. An agent would need additional context to invoke it correctly.

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% with each parameter having a description. The description adds value by listing the format options (CSV, STIX, etc.), but does not elaborate on the other parameters beyond what the schema already provides. As schema coverage is high, a baseline of 3 is appropriate.

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 verb 'Export' and the resource 'IOCs from MISP', and lists the specific formats (CSV, STIX, Suricata, Snort, text, RPZ). This distinguishes it from sibling tools like misp_export_hashes and search tools.

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 description implies usage (when you need to export IOCs in these formats) but does not explicitly state when to use this tool versus alternatives like search or other export tools. No exclusions or when-not-to-use guidance is provided.

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