Show Timesheet Approval Status Filters

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

Annotations indicate read-only and idempotent behavior, but the description does not clearly state what the tool returns. It mentions pagination and metadata, but the reference to 'Field Productivity records' is inconsistent with the endpoint path for timesheet filters, creating confusion.

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 relatively short but includes a misleading sentence about fetching Field Productivity records, which wastes space and hurts clarity. It should be focused on approval status filters.

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?

No output schema exists, so the description should explain what the response contains. It mentions a paginated array and metadata, but the domain (Field Productivity) is likely incorrect. The description is incomplete and unreliable.

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 schema covers all three parameters with descriptions. The description reiterates that company_id is required and page/per_page control pagination, adding no new meaning beyond the schema. Adequate but not enhanced.

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 tool name and title indicate timesheet approval status filters, but the description incorrectly says it fetches 'full details of a specific Field Productivity records by its identifier,' which is inconsistent. The purpose is ambiguous and potentially misleading.

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 like other timesheet filter tools. The description does not clarify the intended use case or provide exclusion criteria.

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