list_time_entries_for_project

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

No annotations are provided, so the description must carry the full burden. It only states the basic operation without disclosing behavioral traits like pagination (the 'top' parameter), sorting, permissions, or whether it returns all entries or supports filtering. This is insufficient for safe invocation.

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 a single sentence, which is concise but under-specified. It fails to provide essential context, making it more of an omission than crafted conciseness. Every word is needed, but more words are needed to be helpful.

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 tool has 2 parameters (one with default) and an output schema (not shown), the description is incomplete. It does not cover parameter usage, output format, or any edge cases. A more complete description would include pagination hints and parameter semantics.

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 0%, yet the description adds no meaning for the parameters. The 'top' parameter (default 0) is not explained, and 'project_id' is only implicit. The agent cannot infer the role of 'top' or that it controls pagination without external knowledge.

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 action 'list' and the resource 'time entries' filtered by project. However, it does not differentiate from many sibling tools like 'list_time_entries' or 'list_time_entries_for_client', which could cause confusion. It is specific enough but lacks distinguishing details.

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. There is no mention of contexts where this tool is preferred, nor any exclusions. The agent receives no help in selecting among the many list_time_entries variants.

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