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

readOnlyHint=true already tells the agent this is a safe read; the description usefully confirms it by citing GET tasks/read and discloses two returned fields (project, status). It adds nothing about pagination behavior, result size, or ordering beyond what the schema already says for limit/offset.

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?

Two short sentences, zero filler, with the functional scope front-loaded and the API endpoint kept as trailing metadata. Nothing is repeated from the schema or annotations.

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 read-only, zero-required-param list tool with full schema coverage, the description covers purpose, returned fields, and the endpoint mapping. With no output schema present it could say a bit more about the response envelope (e.g., paging metadata), but that is a minor gap.

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 100%, so the schema already documents limit, since, offset, is_done, and mother_id in detail. The description only glosses mother_id as "project", adding no filtering semantics of its own – baseline 3 is appropriate when the schema carries the load.

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 and resource ("List tasks") plus the scope that matters for disambiguation: tasks that time can be booked on. Naming the returned fields (project via mother_id, status) and the backing endpoint (GET tasks/read) makes the intent unambiguous, though it does not explicitly contrast with siblings like timetac_list_projects.

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?

Usage is implied by "tasks that time can be booked on" – an agent can infer this is the lookup to run before timetac_create_time_tracking – but no when-to-use/when-not or alternative tools are named. There are also no prerequisites or exclusions spelled out.

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