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

Discloses behavior well beyond annotations: it never creates a remote issue or sends a status transition, records only recovered local linkage/outcome, leaves missing/multiple/mismatched evidence pending review, and states a changed credential cannot redirect the original operation. This resolves the surface tension between 'read-only provider requests' and readOnlyHint=false by clarifying that reads are remote while writes are local.

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?

Front-loads the core action in the first sentence and packs permissions, mutation boundaries, edge-case handling, and parameter sourcing into successive clauses without filler. Dense but every sentence carries information; slightly heavy for a three-parameter tool.

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?

With no output schema and annotations only covering safety flags, the description supplies the missing pieces: required permissions, what is and is not mutated, and how ambiguous evidence is handled. Return shape and idempotency expectations remain unstated, keeping it short of a 5.

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%, so the description must carry the load. It explains intent_id ('the original intent_id from list_ticket_provider_effects') but says nothing about ticket_id or the jira/linear provider enum beyond what the schema already names. Partial compensation for a 3-parameter 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?

States a specific verb and resource ('reconcile' the 'original Jira or Linear intent against provider correlation/status') and scopes it to read-only provider requests. This clearly distinguishes it from siblings like list_ticket_provider_effects, check_ticket_provider_status, and list_ticket_provider_observations.

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 explicit prerequisites (requires integrations:read and tickets:write) and a concrete usage instruction: 'Use the original intent_id from list_ticket_provider_effects.' It lacks explicit when-not-to-use guidance or a named alternative such as check_ticket_provider_status, so it stops short of a 5.

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