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

Annotations already mark it read-only and non-destructive, but the description adds substantial behavioral context: reads use the administrator-connected token, connected=false means no Jira, and it enumerates meanings for jira.state values and sync problem values. This is especially useful because there is no output schema to explain those return fields.

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 description is front-loaded with the purpose and then supplies the necessary state meanings, but it is a dense, run-on paragraph with many semicolon-separated enumerations. It avoids redundancy, though a slightly clearer structure would improve scanability.

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, the description carries the full burden of explaining return values, and it does so thoroughly: connected status, jira.state meanings, summary/status/assignee/link, and sync problem reasons. It gives an agent enough context to interpret likely outcomes without opening other references.

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 sole parameter has 100% schema coverage with an example ('PM-12'), so the schema already explains the key format. The description implies the key identifies the local issue whose Jira link is being read, but adds no further parameter semantics beyond that implication.

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 states a specific verb and resource: it reads which Jira issue an issue is linked to and what that Jira currently reports (summary, status, assignee, link). It distinguishes the read operation from mutation by naming set_jira_link, and it explains the related sync state via get_jira_sync.

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 clearly implies this is the read-side tool for the project's Jira link and explicitly says to use set_jira_link for setting the link. It references get_jira_sync for the status synchronization context, but does not spell out explicit exclusions or when not to use it.

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