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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false. The description adds genuinely useful context beyond them: what text is sent (summary, confirmation questions, live-flow link) and that a disconnected app surfaces an actionable error pointing to Wavelength settings. That is real behavioral disclosure a schema can't convey.

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 two modes, then payload contents, then the connection-error behavior. Every sentence earns its place; the only mild weakness is that the error-handling sentence could be folded in more tightly.

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 6 params, one required, no output schema, and annotations covering the safety profile, the description supplies the missing pieces: mode selection and payload composition. Nothing essential for calling it correctly is absent, though return/confirmation behavior is not described (and needn't be, since no output schema exists to contradict).

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?

Schema coverage is 100%, so the baseline is 3. The description goes further by grouping the parameters into mutually exclusive modes (project_id + issue_type_id for new; issue_key for comment), which clarifies the intended combinations rather than just restating individual field meanings.

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?

States a specific verb+resource (create a Jira issue or add a comment) scoped to a flow, and enumerates the two operating modes. The Jira focus is unmistakable against the many send_flow_to_* siblings, and an agent can tell what the tool produces without opening the schema.

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?

Explicitly routes the agent between the two modes: give project_id and issue_type_id for a new issue, or issue_key to comment on an existing one. It doesn't compare against sibling targets (Confluence, Notion, Salesforce), but the mode-selection guidance is clear and actionable.

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