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

Annotations already establish readOnly/no-destructive/openWorld, and the description adds a genuinely useful disclosure beyond them: feedback is a signal to the Xyle team and performs no mutation on the site. It stops short of stating that repeated submissions are not deduplicated (annotation marks idempotentHint=false), so it is thorough but not exhaustive.

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 sentences, front-loaded with the core action, followed by the effect clarification and a specificity nudge. Dense but every clause carries information; the trailing 'be specific' sentence is slightly instructive rather than definitional but earns its place.

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?

For a low-complexity, five-parameter submission tool with no output schema, the description covers purpose, effect, and required specificity. The only omission is what the caller receives after submitting (acknowledgement vs. ticket id), a minor gap given the absence of an output schema.

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 all five parameters are already documented, including the enum meanings. The description restates the issue categories that match the 'category' enum and hints at the 'tool' parameter ('which tool it concerned') but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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 and resource — reporting a gap or friction the agent hit while using Xyle tools — and immediately enumerates the kinds of issues (missing structure, wrong schema, token-heavy output, errors). No sibling tool performs this function, so there is nothing to confuse it with.

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?

Gives clear triggering conditions with concrete examples and clarifies the scope limitation ('it does NOT change the site'), which steers the agent away from expecting a fix. It does not name an alternative route for actually fixing problems, but for a feedback sink there is no competing tool to route to.

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