misp_get_event

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

Discloses restricted response for TLP:AMBER/RED events, return structure, and attribute limit. Adds value beyond readOnlyHint and idempotentHint 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?

Concise at ~100 words, front-loaded with purpose, structured with return format and restriction note. No wasted words.

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?

Covers return structure and special case; output schema details provided. Lacks error case handling (e.g., event not found) but annotations cover safety and idempotency.

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 0% per context, so description should compensate. It mentions numeric ID and max_attributes but not format details (schema has them). Adds some context but limited.

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 'Fetch one MISP event by numeric ID', listing returned elements. It distinguishes from sibling tools like misp_search_events which retrieves multiple events, and others for IOC lookup.

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?

Describes when to use (fetch by ID) but does not explicitly contrast with siblings like misp_search_events for bulk searching. No guidance on when not to use.

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