Show Timesheet Sub Job Filters

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds that it returns a paginated JSON array and mentions pagination metadata, which is useful but minimal. It does not disclose any additional behavioral traits beyond what annotations already convey. No contradiction with 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 a mixture of sentences that appear to describe two different tools (filters vs. Field Productivity records). It is not concise; it is confusing and could be much shorter and clearer.

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 is provided. The description claims to return a paginated JSON array of Field Productivity records, but the tool is about timesheet sub job filters, so the response structure is unclear and likely incorrect. The description fails to specify what the actual response contains, making it incomplete and misleading.

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% with descriptions for all three parameters. The description reiterates pagination control and required parameter, but does not add significant new meaning beyond what the schema already provides.

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 is confusing: it starts by saying 'Show timesheet sub job filters', but then states 'Use this to fetch the full details of a specific Field Productivity records by its identifier.' This mixes two different purposes. The tool name and title suggest it's about listing filters, but the description implies fetching a single record and then says it returns a paginated array. The purpose is unclear and contradictory.

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 says to use it for fetching Field Productivity records, but doesn't clarify when to use this tool versus other filter or list tools among the many siblings. No when-not-to-use guidance or alternatives are provided.

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