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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description is consistent with those. It adds useful behavioral context beyond annotations: the max limit of 200 and the fact that the response carries pagination.total and has_more, which helps the agent plan pagination.

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 two sentences with no filler. The core scope is front-loaded, the sibling tool usage is stated in the second sentence, and pagination details are included compactly. Every sentence earns its place.

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?

Given the output schema exists and annotations cover safety/idempotency, the description is largely complete: it explains scope, when to use it, and pagination behavior. The only notable gap is the undocumented include_archived parameter, but overall the agent has enough context to invoke the tool correctly.

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?

The input schema describes limit, offset, and search, but the description adds no parameter-level semantics of its own; it only repeats the max limit. The include_archived parameter has no description in the schema and is not clarified in the description, so a meaningful gap remains for that parameter.

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 a specific verb and resource: 'List only projects where the signed-in user is assigned as a team member or project manager and can log project time.' This precisely distinguishes it from other timelog tools like timelog_get_entries or timelog_log_time, and the scope is explicit.

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 description explicitly says to use this tool before timelog_log_time for any project-based time entry, naming the alternative and the condition that selects this tool. This gives an agent clear routing guidance with no need for inference.

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