Show Timesheet Time Type Filters

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

Annotations (readOnlyHint=true, etc.) already indicate safe, idempotent behavior. The description adds pagination details: 'Returns a paginated JSON array... Use page and per_page to control pagination; the response includes pagination metadata.' However, the misleading 'specific Field Productivity records' phrase detracts from 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 not concise due to contradictory and unnecessary content. It front-loads the correct intent but then includes erroneous details about 'Field Productivity records,' which wastes space and undermines clarity.

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?

The tool has no output schema, so the description should explain what the returned filter objects look like (e.g., structure, possible values). It only mentions pagination metadata, leaving the actual response format unexplained. Additionally, the incorrect reference to 'Field Productivity records' suggests the description is incomplete and possibly copied from another tool.

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?

Input schema coverage is 100% with descriptions for all three parameters. The description repeats that company_id is required and mentions page/per_page for pagination, but adds no new semantic information 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 starts with 'Show timesheet time type filters,' which aligns with the tool name, but then contradicts itself by saying 'Use this to fetch the full details of a specific Field Productivity records by its identifier.' This misstatement confuses the core purpose, making it unclear whether the tool lists filters or retrieves a specific record.

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?

There is no guidance on when to use this tool versus its many siblings (e.g., show_timesheet_approval_status_filters, show_timesheet_billable_filters). The description does not differentiate this tool's scope or provide context for when it is appropriate.

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