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

Annotations already establish that this is a safe read-only operation, but the description adds substantial non-obvious context about the returned sync configuration. It explains direction modes, ownerStands behavior when someone can no longer be acted for, webhook status, and the conflict reasons for issues whose statuses are out of step.

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 dense but largely earns its length because no output schema exists and it must define the returned fields. It is somewhat run-on, with many semicolon-separated field definitions, but it is front-loaded with the core concept and avoids unrelated filler.

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?

Given the absence of an output schema, the description supplies the key return-field semantics an agent needs: direction modes, status pairs, actsFor and ownerStands behavior, webhook status, and unresolved issue reasons. Together with the fully described projectKey parameter and read-only annotations, this is complete enough to call and interpret the tool.

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 single projectKey parameter is fully described in the schema, including an example value, so the schema carries parameter documentation. The description refers to 'a project' and project administrators but adds no further parameter meaning beyond the 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?

The description explains that the tool exposes how a project keeps issue statuses in step with Jira, and it enumerates the sync fields returned. It distinguishes itself somewhat by pointing to get_jira_link, but it never states the retrieval action as directly as it could.

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?

The only usage context is the audience note 'For whoever administers the project.' It does not explain when to call this instead of related tools such as get_jira_link, get_jira_connection, or set_jira_sync.

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