list_timesheets

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

Annotations already declare readOnlyHint=true, so the description needs only add behavioral context. It adds the access-scoping fact that only allowed projects/tasks are returned, but it does not disclose pagination, date-range behavior, or how the allowed restriction is enforced. This is adequate but not rich.

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?

A single, front-loaded sentence with no filler. Every word contributes the essential verb, resource, and restriction.

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?

The presence of an output schema and readOnlyHint covers return shape and safety, but with six parameters and 0% schema description coverage, the minimal description leaves date filtering and user filtering unexplained. It is minimally viable for a project-scoped list call but not 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?

Schema coverage is 0%, so the description carries the burden of explaining the six parameters. It only hints at project/task scoping and says nothing about limit, date_from, date_to, or user_id, leaving the agent without meaningful parameter semantics.

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 names a specific action ('List') and resource ('official Odoo Timesheets entries') and adds the key scope ('restricted to an allowed project/task'). This is enough to distinguish it from sibling mutation tools like create_timesheet, update_timesheet, and delete_timesheet.

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?

The phrase 'restricted to an allowed project/task' gives a clear use context and prerequisite, and the read-only purpose is evident. However, it does not explicitly mention alternatives or when not to use the tool, so it stops short of full routing guidance.

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