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

No annotations provided, so the description carries the burden. It discloses that an empty result returns has_task=false, and indicates it is a mirror of Meta MCP tasks_latest, but does not describe side effects, error handling, or whether it is read-only. For a simple lookup this is adequate but not exhaustive.

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 description is front-loaded with the core behavior, then lists required parameter values and an example. It is somewhat long due to the enum list, but each element serves a purpose and the structure (REQUIRED, EXAMPLE) aids parsing.

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 one-parameter tool with no output schema, the description covers purpose, allowed values, example, and a key return behavior (has_task=false). An agent has sufficient information to call it correctly. Minor omissions like error responses are unlikely to block correct usage.

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 provides no description or enum, but the description fully compensates by listing all allowed task_type values and giving an example call. This is high-value, exceeding typical schema-only information.

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 'Return' with resource 'latest completed-or-partial task' and parameter task_type. It also mentions the return value behavior with has_task=false, making the purpose unambiguous. No confusion with siblings like tasks_list which likely lists all tasks.

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 explicit when-to-use guidance or alternatives. The description implies use for fetching the latest task of a type, but does not contrast with tasks_list or tasks_get_status. An agent must infer that this is the correct tool for latest-task queries.

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