Listar registros de tiempo de una tarea

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

No annotations are provided, so the description carries full burden. It discloses the fields returned and ordering but does not mention safety (read-only), required permissions, or potential side effects. Missing details on pagination, error handling, or authentication requirements beyond the token parameter.

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?

Single sentence front-loading purpose and details without extraneous words. Efficiently conveys action, target, and output characteristics.

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?

No output schema exists, so description partially compensates by mentioning returned fields and ordering. However, it omits return format (array?), authentication details, error scenarios, and any limits. Adequate for a simple listing but not fully complete.

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 50% schema description coverage (only token described), the description adds no parameter-level information. It does not explain what 'taskId' represents or how to obtain it. The description focuses on output, not input, so parameters remain under-documented.

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 clearly states the tool lists time entries with specific fields (start, end, pause reason) for a given task, sorted chronologically. It uses a specific verb 'List' and resource 'registros de tiempo de una tarea', distinguishing it from sibling tools like start_task_timer and stop_task_timer.

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 on when to use this tool versus alternatives, no prerequisites or exclusions mentioned. It simply describes function without context on appropriate usage scenarios.

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