list_global_advisories

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the tool lists advisories from the public database, but does not mention pagination, response structure, authentication needs, or any default/filter behavior. The docs link is external and does not compensate within the description itself.

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, front-loaded sentence that clearly states the operation and source, with a useful docs link. No wasted words; it is appropriately sized for a simple list tool.

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 6 optional parameters, low schema coverage, no annotations, and no output schema, the description is too sparse. It lacks guidance on how to filter, pagination limits, and what the response contains, leaving the agent dependent on external docs for confident invocation.

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 low (33%, only 2 of 6 params). The description mentions no parameters or filtering options, so it adds no value beyond the schema. The schema itself leaves 4 params without descriptions, and the description does not help fill that gap.

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 a clear resource 'GitHub Global Security Advisories' and specifies the source 'public GHSA database'. This distinguishes it from siblings like get_global_advisory (singular) and list_repository_advisories (repository-specific).

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 implies this is for listing global advisories and provides clear context (public GHSA database), but it does not explicitly name alternatives or state when to use this tool over get_global_advisory or list_repository_advisories. Usage is implied rather than explicitly guided.

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