List Timecard Entries (Project)

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds value by specifying that the response is a paginated JSON array with pagination metadata and linking to documentation for filtering details. This provides behavioral context beyond the annotations.

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 3-4 sentences long, front-loaded with the action and key details. Every sentence provides useful information, including a link to documentation and API endpoint info. No fluff or redundant information.

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 no output schema, the description explains the return type (paginated JSON array of Field Productivity records with pagination metadata) and links to documentation for filtering. However, it lacks differentiation from sibling tools and does not cover error handling or edge cases, making it adequate 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?

Schema coverage is 100%, so baseline is 3. The description adds context by explaining that log_date, start_date, and end_date are for filtering, and that page and per_page control pagination with metadata in the response. It also explicitly mentions the required project_id parameter, going beyond the schema.

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 that the tool returns a list of timecard entries for the current date and can be used for paginated overview, finding IDs, or filtering. However, it does not explicitly differentiate this tool from other timecard listing tools (e.g., list_timecard_entries, list_timecard_entries_company), leaving the agent unclear about when to choose this specific variant.

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 mentions using the tool for paginated overview, finding IDs, or filtering, but lacks exclusions or alternatives. It does not guide the agent on when not to use this tool or how it compares to sibling tools, which is necessary given the presence of multiple timecard list endpoints.

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