github_security_advisories_get_repository_advisory

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

With no annotations, the description fully bears responsibility for behavioral transparency. It only says 'Get a repository security advisory', omitting details about return format, authentication, rate limits, or side effects. This is insufficient for an agent to understand invocation expectations.

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 no unnecessary words. It is concise and front-loaded, but could benefit from additional context without sacrificing conciseness.

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 the absence of annotations and output schema, the description is too brief. It does not explain the return type, prerequisites (e.g., ghsa_id format), or how the output relates to other advisory tools. The tool's complexity is moderate, but the description leaves many gaps.

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 input schema provides parameter descriptions that are merely the parameter names ('owner', 'repo', 'ghsa_id'), offering no semantic value. The description adds no additional meaning to these parameters. With 100% schema coverage but poor descriptions, the description fails to compensate.

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 'Get a repository security advisory' clearly states the action (get) and resource (repository security advisory), distinguishing it from sibling tools like list, create, or update. However, it does not explicitly differentiate from get_global_advisory beyond the word 'repository'.

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?

No usage guidance is provided. The description does not specify when to use this tool versus alternatives like list, create, or update. It does not mention that this requires a known ghsa_id or that it is for fetching a single advisory.

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