get_issue_tasks

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered without the description. The description adds nothing behavioral beyond that — no return format, no pagination, no ordering — so it does not earn credit above the annotation floor.

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 and short, but the second sentence is a near-verbatim restatement of the first, adding only 'using its unique identifier.' Half the text is redundant padding rather than new information.

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 simple read-only list getter with full annotation coverage, the essentials are present, but it lacks return-shape and pagination detail and offers no routing among the many sibling task tools. Adequate but not complete for the surrounding tool set.

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 reported at 0%, so the description must compensate. 'Using its unique identifier' hints that the issue's ID is the lookup key, marginally reinforcing the nested issueId field, but it gives no format, type, or nesting detail beyond what the schema structure already shows.

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 clear verb+resource: 'Get all tasks for an issue.' An agent knows exactly what it does, but the description never distinguishes it from siblings like get_issue_task (singular) or get_my_issue_tasks_collection, so the second sentence only rephrases the first rather than differentiating.

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?

There is no when-to-use guidance and no mention of alternatives, exclusions, or prerequisites. Usage is only implied by the tool name, which is weak given the several near-identical sibling task retrievers.

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