List CVEs (Exposure Analytics)

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

Annotations declare readOnlyHint and idempotentHint, so the agent knows this is a safe read operation. The description adds that filters are optional, which is useful, but it doesn't disclose any additional behavioral traits such as pagination, default limits, or data source nuances.

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, clear sentence of nine words, front-loaded with the key information. Every word earns its place with no filler.

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?

The tool is simple but the description omits details about the query filter structure and the return format, especially since there is no output schema. The lack of pagination/filter guidance makes the description incomplete for reliable invocation.

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?

The schema has one opaque 'query' parameter with arbitrary properties and 0% coverage. The description mentions 'optional filters' but doesn't explain what filters are available or how to structure the query object, leaving the agent without enough information to correctly construct arguments.

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 lists CVEs from Exposure Analytics, using a specific verb and resource. It distinguishes between list and get/export operations implicitly through the wording, though it doesn't explicitly name alternatives.

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 is given on when to use this tool versus sibling tools like cymulate_ea_cves_get or cymulate_ea_cves_export. The description implies usage for listing CVEs but doesn't provide context for choosing it over alternatives.

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