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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that this is a static catalog of checks keyed to CWEs, which usefully signals that nothing is executed against the user's code. It says nothing about the size of the catalog or the shape of the returned entries.

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?

Two functional sentences, front-loaded with the resource definition before the usage guidance. The trailing vendor/served-by line is boilerplate that does not help an agent decide or call, but it is short and harmless.

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 no parameters and no output schema, the description carries the burden of signaling what comes back; it does so at a high level (a CWE-mapped catalog of checks). It stops short of describing the fields of each check entry, which is a minor gap for a simple no-arg list tool.

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 tool takes zero parameters (empty object schema at 100% coverage), so there is no parameter meaning for the description to add. Baseline for a no-parameter tool applies.

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?

States a specific resource: the catalog of CI/CD security checks vu1nz runs, each mapped to a CWE. That is concrete and distinct from the siblings that fetch advisories, blog posts, or run an actual scan. It does not explicitly name a sibling to contrast itself with, which keeps it from a 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?

'Use to explain to a user what vu1nz would catch on their PRs' gives a clear trigger for invoking it. It implicitly separates the catalog from an actual scan, but never states when NOT to use it or names vu1nz_scan_repo as the alternative for real repo evaluation.

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