workflow_get_integration_diagnostics

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read. The description adds useful behavioral context that annotations do not cover: results are 'evidence-labelled' and carry an 'observation time', which hints at provenance and freshness semantics. It stops short of explaining what 'evidence-labelled' means or how stale results can be.

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?

A single front-loaded sentence that states the action, the scope, and the two distinguishing output traits with no filler. Nothing is redundant or padded.

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 zero parameters, the description is the only source of return-value information, and it only gestures at it via 'evidence-labelled' and 'observation time'. It is enough to call the tool correctly, but the agent gets no sense of diagnostic shape, severity fields, or failures.

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 per the rubric the baseline is 4; there is nothing for the description to disambiguate. No parameter detail is added or needed.

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 (read) and resource (integration diagnostics) and enumerates the covered systems (Jira, Confluence, GHES, Jenkins, Splunk), so the agent knows exactly what surface this covers. It does not explicitly contrast itself with sibling read tools like workflow_get_freshness or workflow_get_task_audit, which keeps it short of a 5.

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?

There is no statement of when to call this versus alternatives such as workflow_get_freshness or workflow_get_related_artifacts, nor any prerequisite or exclusion. The implied usage (fetching integration health diagnostics) is inferable from the purpose but never spelled out.

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