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

Discloses 'Upstream maintenance mode; 2-min timeout, 5GB/query limit' which adds valuable constraints beyond the readOnlyHint annotation. No contradiction with 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?

Three sentences, no wasted words: purpose, usage hint, and technical constraints are front-loaded and efficiently presented.

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 complexity of a custom script tool, the description covers purpose, constraints (timeout, size), and input requirements. No output schema exists, but return value is implied. Could mention error handling, but overall adequate.

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% with parameter descriptions; description adds 'Script must define main()' for the script parameter, which slightly enhances understanding 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?

Description explicitly states 'Run a custom JQL script for arbitrary analysis' and labels it as 'Power-user escape hatch', clearly distinguishing it from sibling tools like mixpanel_segmentation or mixpanel_retention.

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?

Indicates it's a 'power-user escape hatch' implying use when other tools are insufficient, and mentions 'Script must define main()' as a prerequisite. However, it lacks explicit when-not-to-use or direct comparisons to siblings.

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