cwe_lookup

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

No annotations are provided, so the description carries full burden. It mentions it returns results for 'top 40+ most common CWEs' but does not disclose what happens for unrecognized IDs, keyword matches with no results, or any other limitations. The phrase 'top 40+' is vague and may mislead users into thinking all CWEs are covered.

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 covers the essential elements: action, resource, parameters, and output. It is concise without being overly terse, though it could be slightly more organized with separate sentences for each mode.

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 description explains the output (name, description, category) and covers the two main use cases. However, it lacks details about error handling (missing ID, no results), pagination, or whether results are limited to only the top 40+ CWEs. Given the low complexity of the tool, this is adequate but not complete.

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%, so baseline is 3. The description adds valuable context beyond schema: it specifies the format for the 'id' parameter ('CWE-79' or '79') and the purpose of 'query' (search keyword). This helps users correctly populate parameters.

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 action ('Look up'), the resource ('CWE'), and the two modes of operation (by ID or by keyword). It distinguishes from siblings by being the only CWE-specific tool among many CVE-related ones.

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 explains when to use each parameter ('by ID' or 'by keyword'), implying the two use cases. It does not explicitly mention when not to use this tool or provide alternatives, but for a simple lookup this is adequate.

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