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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds only a generic note that MCP approval requirements are configurable by the org administrator and that business workflow approvals always apply — boilerplate that does not describe this tool's behavior, its pagination, or filtering, and is arguably irrelevant to a read operation.

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 core purpose is front-loaded in one short sentence. The trailing approvals sentence is unrelated boilerplate that an agent would likely misread as relevant to this call, so the definition is short but not efficient.

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 not be described, but the definition leaves undocumented parameters at 0% schema coverage and gives no guidance on template selection or scope. For a list tool surrounded by at least three similar template-listing siblings, this is insufficient.

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?

The schema has 0% description coverage across three parameters (limit, offset, search), so the description must compensate and it says nothing about any of them. The conventional names hint at paging and free-text search, but the maximum limit of 100, default paging size, and search field coverage are never explained.

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?

The description opens with a clear verb+resource pair, 'Find task templates', which tells an agent precisely what the tool returns. It does not, however, separate this from near-siblings such as list_task_template_items, list_project_task_templates, or get_task_template, so an agent must infer scope from names alone.

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 statement of when to use this tool versus the many alternatives (get_task_template for a single item, list_task_template_items for items within a template). The only supplementary sentence concerns approval configuration, which gives no usage direction for a read-only list call.

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