misp_cache_feed

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

No annotations provided. Description hints at a non-destructive operation ('without creating events'), but does not disclose side effects, authentication needs, or rate limits. For a caching tool, more behavioral context is needed.

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 that is direct and front-loaded. Every word 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?

Given the simplicity (one parameter, no output schema), the description is somewhat complete but lacks usage guidelines and behavioral transparency. Adequate for a simple tool but has gaps.

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% for one parameter (feedId). The description provides context for the overall operation but does not add meaning beyond the schema's description for feedId. Baseline 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?

Description clearly states caching feed data locally for correlation, and explicitly says 'without creating events', distinguishing it from misp_fetch_feed. The verb 'cache' and resource 'feed data' are specific.

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?

Implied usage for offline correlation without event creation, but no explicit guidance on when to use this tool versus siblings like misp_fetch_feed or misp_toggle_feed. No prerequisites mentioned.

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