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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing about behavior for this read tool and instead offers a sentence about approval configuration that reads as boilerplate and is confusing in the context of a read-only listing.

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?

The first sentence is efficient and front-loaded. The second sentence about MCP approval requirements does not earn its place – it is unrelated to listing templates and consumes half the description.

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?

An output schema exists so return values need no explanation, but the three undocumented query parameters, absent usage guidance, and missing differentiation from list_task_templates / get_project_task_template leave meaningful gaps for a paginated list tool.

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% – limit, offset and search carry no descriptions or constraints beyond types and defaults. The description does not mention pagination or searching at all, so an agent gets no help on how to page or what `search` matches.

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?

"Find project task templates" states a clear verb and resource, so an agent knows this retrieves templates. However, it does not distinguish itself from close siblings such as list_task_templates (a different resource) or get_project_task_template (single fetch), so the agent must infer the boundary.

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?

No when-to-use guidance, no prerequisites, and no alternatives named. The tool sits in a dense cluster of ~300 siblings including list_task_templates and get_project_task_template, and the description gives no signal about which to pick.

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