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

The readOnlyHint annotation already signals a safe read operation. The description adds the scope 'authenticated user's tasks' and the REST path 'GET /api/tasks', which reinforces the read-only nature and adds endpoint context. However, it does not disclose pagination behavior, return format, or ordering, so it provides limited extra value beyond annotations.

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 concise, consisting of one clear sentence plus a REST endpoint reference. Every word adds value, and the most critical information (list tasks) is front-loaded.

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 listing tool with no parameters, the description covers the essential scope (authenticated user) and the endpoint. Given the readOnly annotation and absence of an output schema, it is sufficiently complete, though it could optionally mention pagination or result summary, which is not necessary.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description does not need to add parameter details, and any parameter-related info would be redundant since there are none.

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 explicitly states the verb 'List' and the resource 'tasks' with scope 'authenticated user's tasks', making it clear this is a list operation. The plural 'tasks' distinguishes it from reclaim_get_task (singular). The REST method GET further clarifies the action.

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 guidance is given on when to use this tool versus alternatives like reclaim_get_task, reclaim_list_habits, or other task-related siblings. It does not mention any exclusions, prerequisites, or when not to use it, leaving the agent to infer from the name.

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