Export CVEs

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

The description is consistent with the readOnlyHint and idempotentHint annotations. It adds minimal behavioral context by mentioning the output format, but does not disclose any other behavioral traits such as response structure or potential errors.

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 extremely brief, but this brevity comes from under-specification rather than efficient communication. It provides only a single sentence with a parenthetical, leaving out critical information about parameters and usage.

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 presence of an unannotated `query` object and no output schema, the description is insufficient to fully understand how to invoke the tool and what the response will contain. It mentions format but not the query semantics or response details.

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 defines a `query` object with no detailed structure, and the schema coverage is 0%. The description does not mention the `query` parameter at all, leaving the agent without any semantics for what can be passed.

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 states the tool exports CVEs and notes the typical format (CSV/JSON download), which is clear. However, it is essentially a restatement of the title and does not differentiate from related tools like cymulate_ea_cves_list or cymulate_ea_cves_get.

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 provided on when to use the export tool versus listing or getting individual CVEs, nor any mention of alternatives. The description entirely omits any usage context.

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