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

Goes well beyond the annotations by disclosing that origins are fixed hosted only, that there are no remote writes, that immutable IDs are pinned only after a matching response, that unknown attempts are never redispatched, and the required scopes (integrations:read, tickets:write). 'No remote writes' refines rather than contradicts readOnlyHint=false, since local linking still mutates state.

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-loaded with the purpose, then provider formats, then credential/retry/security constraints. It is dense and long but nearly every clause carries distinct operational information, with little redundancy.

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 complex nested-object, multi-provider tool with no output schema, the description covers identification formats, credentials, idempotent retry, and auth scope. The gap is expected_revision, a required concurrency token that is never explained, and no description of the pinned-field result.

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 coverage the description carries the load and mostly succeeds: it maps container/item to each provider's real-world identifiers (owner/repo+issue, project ID+iid, org/project UUID+work item ID, etc.) and explains credential_id and request_id reuse. It leaves expected_revision and ticket_id unexplained, which keeps it from 5.

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 opening sentence states a specific verb+resource ('Link and check one explicitly selected remote item') and the body enumerates exactly what a remote item is per provider. It is clear enough to distinguish from check_ticket_provider_fields and list_ticket_provider_fields, though it never names a sibling explicitly.

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 real conditional guidance: new providers need an exact configured credential_id while Jira/Linear reuse existing owner Settings credentials, and lost replies should reuse the same request_id/arguments. Lacks an explicit 'use this instead of check_ticket_provider_fields' routing statement, so it falls short of 5.

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