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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the business meaning of view=unbilled and the underlying GET /v2/timeslips endpoint, but says nothing about pagination behavior, default page size, or what ordering results come back in.

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 dense sentence plus a one-line endpoint reference, with the filterable dimensions and the unbilled view front-loaded. No filler.

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 list tool with 10 optional params, full schema coverage and no output schema, the description plus schema give an agent enough to call it correctly. It falls just short of complete by omitting pagination/ordering context that a listing tool would benefit from.

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 all ten parameters are already documented in the schema, including defaults and formats. The description's mention of date range, user, task, project and view maps to parameters but adds no syntax or semantics beyond what the schema provides; baseline 3 applies.

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+resource ('List logged time') and enumerates the filterable dimensions, so it is immediately distinguishable from the sibling freeagent_create_timeslip, which writes a timeslip rather than listing them.

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?

It implies when the tool applies by listing filters and calling out view=unbilled for 'time not yet invoiced', which is genuine context. However, it never states when to prefer this over alternatives or any preconditions, so usage must be inferred.

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