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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact not in the annotations: results are automatically scoped to the caller's own customer. It omits pagination/limit behavior and return ordering, so the addition is modest.

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 tight sentences with zero filler; the core operation and its filters are front-loaded and the scope caveat is appended immediately after.

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 6-parameter list tool with no output schema and no parameter descriptions in the schema, the description should say more about the unmentioned 'limit' parameter, pagination, and default ordering. It covers the filter surface adequately but leaves the result-shaping behavior undocumented.

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 0%, so the description must carry parameter meaning; it does name five of the six params as filter dimensions (status/priority/area/type/project), which is real compensation. But it omits 'limit' entirely and gives no value formats, defaults, or multiplicity beyond the enum values in 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?

States a specific verb and resource (list support tickets) plus the filterable dimensions, so an agent can distinguish it from the singular get_support_ticket and the file_support_ticket mutation. It does not explicitly name or differentiate against those siblings, but the scope sentence makes the operation unambiguous.

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 filter list implies when the tool is useful (browsing/searching tickets by attribute), and the 'scoped to your own customer automatically' clause gives context about result scope. However, there is no explicit when-to-use versus get_support_ticket or when-not guidance, so usage is only implied.

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