Show Timesheet Employee Filters

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

Annotations already indicate read-only and idempotent behavior. The description adds that it returns a paginated JSON array with pagination metadata and specifies the endpoint. However, the internal inconsistency between timesheet filters and Field Productivity detracts from clarity.

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 six sentences and somewhat repetitive, mixing two purposes. It could be more concise by focusing on the actual function and removing the confusing reference to Field Productivity.

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 is simple but the description fails to explain what 'employee filters' are or how they relate to timesheets. The mention of 'Field Productivity records' is unexplained, and without an output schema, the agent lacks understanding of return fields.

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 description coverage is 100%, so all parameters are already documented. The description reinforces the required 'company_id' and pagination behavior but does not add significant new meaning 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 mixes two different concepts: 'timesheet employee filters' and 'Field Productivity records'. The first sentence says 'Show timesheet employee filters' but then states 'fetch the full details of a specific Field Productivity records', which is vague and potentially misleading. It does not clearly state what the tool returns.

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 show_timesheet_*_filters siblings. The description only mentions pagination but does not specify context or exclusion criteria.

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