Show Timesheet Billable Filters

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

Annotations already indicate it's read-only and idempotent. The description adds pagination details (page, per_page, metadata) but also includes an inconsistent claim about fetching a specific record, which undermines transparency.

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 5 sentences. The first sentence is redundant with the title. The second sentence is inaccurate and should be removed. The remaining sentences are functional but could be consolidated. Not maximally concise.

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 must explain the response. It mentions a paginated JSON array of records and pagination metadata, which is helpful, but the conflicting claim about a single record and lack of detail on the filter structure makes it incomplete.

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 already covers all parameters (100% coverage). The description adds value by explaining that page and per_page control pagination and that the response includes pagination metadata, which goes beyond the bare schema descriptions.

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 name and title clearly indicate 'timesheet billable filters', but the description introduces confusion by saying 'fetch the full details of a specific Field Productivity records by its identifier' which contradicts the notion of a filter list and the endpoint path. The primary purpose is discernible but not clearly stated.

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 provides no guidance on when to use this tool versus the many sibling filter tools (e.g., show_timesheet_approval_status_filters). It incorrectly suggests fetching a specific record, which is misleading for a filter-list tool.

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