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

Adds substantial behavior beyond annotations: 'Never returns payloads', 'bounded newest-first page', pagination contract via next_before_id/has_more, 'No provider request, retry or reconciliation', and required permissions ('Requires integrations:read and tickets:read'). This is rich disclosure annotations don't provide.

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?

Dense, front-loaded and waste-free: purpose, fields, payload exclusion, pagination, side-effect scope, and permissions in a few tight sentences. Every clause 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?

No output schema or schema descriptions, so the description carries return-value and parameter burden; it largely does (fields, payload exclusion, pagination, pagination cursor behavior). Missing only explicit correlation between the enum provider param and the list, and ID format details, keeping it just under complete.

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?

With 0% schema description coverage, the description must compensate. It documents the limit default/max (20/50), the pagination cursor (next_before_id, paired with has_more), and provider scope (GitHub, GitLab, Asana). It doesn't fully explain before_id or the ID format expectations, but it meaningfully covers most parameter semantics.

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 and resource ('Read a bounded newest-first page of one owned ticket’s recorded GitHub, GitLab and Asana write effects') with an explicit field list (operation, target status, state, last outcome, correlation ID, timestamps). This clearly distinguishes it from sibling list_ticket_provider_effects and list_ticket_integration_connections by scoping to recorded write effects.

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?

Gives strong usage context ('Default 20, maximum 50; use next_before_id while has_more') and an important exclusion ('Never returns payloads. No provider request, retry or reconciliation'), routing agents away from retry/reconcile siblings. It does not name the specific sibling alternative (e.g., reconcile_ticket_provider_effect) explicitly, so it's clear context without full alternative naming.

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