audit_log

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds pagination behavior and attribution fields, but omits whether it is read-only (though implied) and does not explain response structure or account filtering. Partial transparency.

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 that is front-loaded with the core purpose ('Paginated mutation audit trail') and contains no extraneous words. Every phrase 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?

Despite an output schema, the description is insufficient for a tool with 0% schema coverage and no annotations. It fails to explain the account filter and does not provide enough guidance for correct invocation, especially for differentiating this tool from similar audit/log tools.

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 0%, and the description does not compensate. 'Paginated' hints at limit/offset, but the account parameter is completely unexplained, leaving the agent to guess its purpose. The description adds minimal parameter 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?

The description clearly identifies the tool as a paginated audit trail for mutations, specifying agent and idempotency attribution. This distinguishes it from other listing tools and clearly states the resource and action.

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 phrase 'mutation audit trail' implies when to use this tool (to inspect mutations), but it does not explicitly name alternative tools or provide when-not-to-use guidance. No exclusion criteria are given, so usage context is only implied.

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