github_check_vulnerabilities

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

No annotations are provided, so the description carries full burden. It discloses it checks vulnerabilities and detects specific alerts, but does not mention whether it is read-only, required permissions, rate limits, or what happens on errors. Behavioral transparency is minimal.

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 concise: two sentences with no wasted words. It front-loads the main action and includes the specific alert codes.

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 no annotations and no output schema, the description lacks completeness. It does not describe return values, error cases, or what constitutes a 'critical' vulnerability. For a security tool, more context would be valuable.

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% with both owner and repo having descriptions. The description adds context about what the tool does (checking vulnerabilities) but not additional parameter meaning beyond the schema. Baseline 3 is appropriate.

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 tool checks for 'critical known vulnerabilities and stale unfixed alerts (>90 days)' and explicitly mentions it 'detects SUP-004, SUP-005'. This provides a specific verb and resource, distinguishing it from sibling tools that check other aspects like secret scanning or dependabot updates.

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 gives no guidance on when to use this tool versus alternatives. With a long list of sibling tools, explicit usage context (e.g., when to use github_check_dependabot instead) is missing.

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