List Audits

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

No annotations provided. The description only states it provides 'key details and statistics' without clarifying if it's read-only, pagination behavior, or rate limits. For a read operation, agents benefit from explicit safety hints.

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?

Single sentence conveying purpose efficiently. No redundant words, though could be slightly more structured. Still earns a 4 for minimal fluff.

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?

No output schema, so description should clarify return format. Only vaguely mentions 'key details and statistics'. With 5 optional parameters, lacks completeness on pagination, defaults, and response structure.

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 100% with each parameter having a description. The description adds 'key details and statistics' but does not enhance parameter meaning beyond 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 the verb 'retrieves a list', resource 'website audits', and scope 'all associated with your account'. It distinguishes from sibling tools like create, delete, or get single audit by specifying listing all audits.

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 guidance on when to use this tool versus alternatives like getAuditReport or getAuditHistory. Implied usage for listing, but no explicit context or exclusions.

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