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

With no annotations, the description carries the transparency burden and does well: it discloses pagination (including independent pagination for section assessments), the source object, the categories of data included, and explicitly states that these findings do not alter numerical scores. It does not cover auth requirements or failure modes, but for a getter this is a strong disclosure.

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?

Two sentences, front-loaded with the core purpose, with no filler. The scope and the critical non-scoring behavior are stated compactly.

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 high-level purpose is clear, but with no output schema and no annotations the description should also convey return shape, pagination parameter behavior, and what includeDismissed means. It partially describes returned contents, but an agent still lacks enough detail to invoke it confidently.

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 coverage is only 33% because only pageSize has a description, and the description does not compensate by explaining offset or includeDismissed. It repeats the notion of pagination but adds no semantics for the undocumented parameters beyond what the schema already provides.

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 names a specific verb and resource: 'Get paginated audit findings and independently paginated section assessments from the published Audit rollup.' The detail about exact excerpts, remedies, versions, and coverage states disambiguates it from the sibling devtune_get_audit_summary and other get_* tools.

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 gives context (published Audit rollup, findings vs. numerical scores) that implies when to use it, but it never explicitly states when-not-to or names an alternative like devtune_get_audit_summary. The 'do not change numerical scores' note is an indirect exclusion rather than an explicit routing instruction.

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