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

Beyond the readOnly/idempotent/destructive annotations, the description adds meaningful behavior: events are 'compact', integration-delivery attempts are 'redacted', and pagination is 'bounded keyset'. These details tell the agent about response scope and paging mechanics, which annotations alone do not convey.

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 tight sentences: the first states the core purpose and scope, the second adds endpoint equivalence and pagination behavior. No filler or redundancy; key facts are front-loaded.

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?

For a 17-parameter tool with no required params and a rich schema plus output schema, the description supplies the essential orientation: business scope, redaction, and paging behavior. It does not enumerate filter grouping, but the 82% schema coverage and output schema fill most practical 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?

Schema description coverage is 82%, so the schema already carries most parameter meaning; the baseline of 3 applies. The description adds only a high-level 'business-scoped' and 'bounded keyset pagination' signal that corroborates the business_id and cursor/limit parameters without detailing them.

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 opens with a specific verb-object pair—'List a business-scoped timeline of compact call-runtime events and redacted integration-delivery attempts'—which clearly identifies the resource and scope. The endpoint mirror (GET /api/v1/observability-events) reinforces that this is uniquely the observability-events listing tool among siblings.

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 conveys that this is the right tool for reading business-scoped observability events, but it never states explicit when-to-use/when-not-to-use conditions or names alternative tools. Usage is implied by the event-domain vocabulary rather than stated as guidance.

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