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

The description explicitly discloses the stateful nature of the operation ('STATEFUL — creates a comment on the issue') and explains the conversion to ADF. Annotations already indicate non-read-only and non-idempotent, so the description adds useful context about the side effect without contradicting annotations.

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?

Two concise sentences: the first states the primary purpose, the second adds key details about conversion and side effects. Every sentence earns its place with no redundancy or fluff.

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 tool's complexity (5 parameters, nested test_suite object, output schema exists), the description is sufficiently complete. It explains the tool's role, side effects, and content transformation. It doesn't cover error scenarios, but that is not expected given the output schema and annotations.

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 description coverage is 100%, so the baseline is 3. The description adds value by linking the test_suite parameter to the output of jira_to_test_suite and by mentioning the content (Gherkin, E2E steps, API tests, ambiguities) that will be converted, which helps the agent understand what to pass.

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 clearly states the tool's function: posting the output of jira_to_test_suite as a formatted comment on a Jira ticket. It specifies the resource (output of jira_to_test_suite), verb (post), and target (source Jira ticket), distinguishing it from siblings like create_confluence_page or fetch_jira_issue.

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 description implies a clear workflow: use this tool after jira_to_test_suite to post its output. It provides context on the intended scenario, though it does not explicitly state exclusions or alternatives, such as not using it for generic Jira comments.

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