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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description adds behavior beyond them: page caps above 100 with disclosure and the need to follow nextCursor for exhaustive lists. It does not mention ordering of results or what an empty page means, which keeps it from a 5.

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?

Front-loaded with the resource scope, then filter and pagination behavior, with no filler sentences. The second sentence ("Platforms distinguishes example code languages from platform names and classes") is compressed to the point of being hard to parse on first read.

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?

With an output schema, full schema descriptions, and annotations present, the description only needs to add routing and behavioral context, which it does for filtering, capping, and pagination. Coverage of how the topics relate to sibling tools is the remaining gap.

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 the baseline is 3; the description earns above that by explaining the non-obvious filter matching rule (tokens match at word starts or camelCase humps, with the "script finds JavaScript" example) and by clarifying that platforms mixes example-code languages with platform names and classes. The limit cap and cursor semantics largely repeat the schema.

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?

Opens with a specific verb and resource ("List loaded CWE/CAPEC vocabulary") and enumerates the topic families it covers, which clearly separates it from the get_/search_ siblings. The trailing "or" chaining of views, workflow, and versions makes it read as a grab-bag rather than a crisp statement of one purpose, so it falls short of 5.

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?

"omit filter to browse" plus "Follow nextCursor for complete lists" gives concrete when-to guidance for the two main usage modes. It stops short of explicitly routing the agent away from cwe_search_weaknesses or cwe_get_view, so there is context but no exclusions.

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