classify_model_cwe

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

With no annotations, the description fully discloses behavior: re-validation against catalog, skip logic, force option, return summary fields, and error condition. This gives a complete picture of the tool's operation.

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?

Description is concise, with front-loaded purpose and structured details using dashes. Every sentence adds value without redundancy.

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?

Despite having an output schema, the description already summarizes return fields. It covers prerequisites (CWE enabled), skip logic, grounding, and error cases. Missing minor detail about 'server_version' but overall 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 67% (2 of 3 params described). Description adds meaning for 'force' and 'model_id' but does not clarify 'server_version'. The description compensates partially but leaves a gap.

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 the tool classifies a model's control objectives against the CWE catalog. It differentiates from sibling tools like get_cwe_catalog and get_model_cwe_tags by focusing on classification rather than retrieval.

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?

Description provides context on when to use (for classification), skipping already tagged objectives unless forced, and a 404 if CWE is not enabled. However, it does not explicitly mention alternatives or exclusions compared to siblings.

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