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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real value by disclosing the sort order (newest first) and the dual-mode behaviour where issue_id silently switches the endpoint to a message thread. It does not address pagination beyond the schema's limit field, and the trailing 'Read tier' is unexplained jargon, so it falls short of a 5.

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 scope and sort order, then alternates, then the read-tier note — all three sentences earn their place and there is no filler. It is dense and packs three distinct concerns into one breath, and the unexplained 'Read tier' fragment costs it a point.

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 no output schema and five optional parameters, the description covers what an agent needs to choose correctly: filtering dimensions, the thread-mode escape hatch, and the sibling to use otherwise. It omits any hint of result shape or how limit interacts with the 'newest first' ordering, which is a modest gap rather than a blocker.

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?

At 40% schema coverage the description must compensate, and it does: it enumerates the status values (OPEN, ACKNOWLEDGED, IN_PROGRESS, RESOLVED, CLOSED, or a comma list) that the schema leaves as a bare string with no enum, and clarifies that project_id and site_id act as filters while issue_id overrides the whole operation. Only limit lacks any description-side context beyond the schema's '1-200 (default 100)'.

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 (org-wide issues inbox, GET /issues) with explicit scope: every task issue across projects, newest first. It also names the two sibling behaviours it is not (tascan_list_issues for a single list, thread read via issue_id), so an agent can distinguish it without opening any 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?

Explicit routing rules: use tascan_list_issues for a single list, and pass issue_id instead to read one issue's message thread. Both the when-to-use and the when-not-to-use alternative are spelled out rather than implied.

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