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

Annotations only declare readOnlyHint, but the description adds substantial behavioral context beyond that: the sync semantics (external issue created once, timeline events follow as comments, metadata edits pushed as updates), the per-entry delivery-health fields (last_synced_at, last_error and why), and a security caveat that tracker credentials must never be pasted into chat.

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 safety warning and the 'always call before answering' rule are front-loaded and the entry contents are grouped sensibly, but the first sentence is a long run-on and the closing 'Read-only.' largely restates the readOnlyHint annotation. Slightly dense, though nearly every clause carries information.

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 input parameters and no output schema, the description compensates by enumerating the fields each entry returns (provider, destination, enabled state, sync filters, delivery health) and explaining how connections are created and fixed. An agent has everything needed to call it and interpret the 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?

The tool takes zero parameters, so the baseline is 4; the description correctly implies a full-organisation listing with no filtering inputs. There is nothing further to document in the parameter space.

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 names a specific verb and resource ('List the organisation's TICKET SYNC CONNECTIONS') and immediately defines what a connection is (a Jira project, Linear team, or signed webhook endpoint that tickets mirror to). The parenthetical enumeration makes the resource unambiguous even among the many list_* 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?

It gives an explicit imperative: 'ALWAYS call this before answering whether Ankra tickets can sync or connect to Jira, Linear, an issue tracker, or any external system - never assert that no integration exists without reading it.' That is a clear when-to-use plus a when-not-to-do (never assert absence without checking), and it also points to where connections are actually managed (admin POST/PUT API).

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