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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the safety profile is covered. The description adds useful behavioral detail beyond them: results come from the latest run only, results are 'top' issues (ranked/capped), and the default page size is 25 with a hard cap of 200.

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?

Three short sentences, no filler, front-loaded with the resource and scope before the optional filter and return cap. Every sentence earns its place.

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, so the description carries the return-value burden; it does state that up to `limit` instances are returned, which is adequate. It stops short of indicating what an 'issue' record contains (fields, severity distribution), leaving a minor gap for a tool with no output schema.

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 100%, so the baseline is 3, and the description adds genuinely new information not present in the schema: the default limit of 25 (the schema only states the 1-200 range) and the allowed severity vocabulary context.

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?

States a specific verb+resource ('get ... issues from the latest audit run for a site') and pins the scope to the most recent run. It does not explicitly differentiate itself from the sibling get_site_audit, which an agent could easily confuse it with.

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?

Usage is only implied: the description mentions an optional severity filter, from which an agent can infer when to narrow results, but there is no explicit when-to-use statement, no prerequisites, and no guidance on choosing between this and get_site_audit or get_site_changes.

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