list_repository_advisories

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

With no annotations provided, the description carries full behavioral disclosure burden. It only says 'List repository security advisories', which implies a read operation but does not disclose pagination behavior, authentication requirements, rate limits, or response structure. It adds no context beyond the obvious action.

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 sentence with a direct verb-object structure, followed by a documentation link. It is concise, front-loaded, and contains no filler or redundant information.

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?

There is no output schema, no annotations, and the description does not explain return values, pagination, or how to use the parameters. For a list operation with four parameters, the description is too sparse to fully inform an agent, despite the documentation link.

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 only 50%: 'page' and 'per_page' lack descriptions. The tool description does not compensate by explaining these or any parameters, leaving the agent without additional semantic guidance for pagination parameters. The description adds no parameter meaning beyond 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?

The description clearly states 'List repository security advisories', specifying the verb 'List' and the resource 'repository security advisories'. This distinguishes it from sibling tools like 'get_repository_advisory' (singular) and 'list_global_advisories' (global scope), making the purpose unambiguous.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that this is for repository-specific advisories only, nor does it compare with 'list_global_advisories' or 'get_repository_advisory'. The description provides no usage context or exclusions.

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