list_dependabot_alerts

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

No annotations are provided, so the description carries the full burden. It discloses the critical `security_events` PAT scope requirement, which is valuable. However, it does not describe return format, default filtering behavior, or other behavioral traits that an agent might need.

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 concise sentence followed by a documentation link. It is front-loaded with the action and resource, and every element is relevant and useful.

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 tool has eight parameters and no output schema, but the schema documents filters well. The description adds the auth requirement and directly scopes the resource. It lacks explicit mention of pagination defaults or return structure, but the docs link and schema cover much of this, making it adequate for a list operation.

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 description coverage is 75%, and the description adds no parameter-specific meaning beyond 'for a repository', which is already captured by the required owner/repo fields. It does not compensate for the remaining 25% of parameters without descriptions.

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 uses the specific verb 'List' with the resource 'Dependabot alerts' and scopes it to 'a repository', clearly distinguishing it from get_dependabot_alert and other alert listing tools. The name itself is also descriptive.

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 provides repository-level context but does not explicitly state when to use this tool versus get_dependabot_alert or alternative alert listing tools like list_code_scanning_alerts. The scope requirement is useful but not a substitute for usage guidance.

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