Show Timesheet Crews Filters

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

The description misrepresents the tool as fetching a specific record, while it actually returns a paginated list. Beyond annotations (readOnlyHint, idempotentHint), it adds confusion by referring to Field Productivity records instead of timesheet crews filters. Pagination behavior is mentioned but no details on response structure beyond 'JSON array'.

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 concise but includes API endpoint details that could be omitted or streamlined. The conflicting statements waste space; front-loading is poor due to initial contradiction.

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 detail the response fields. It only mentions 'pagination metadata' and 'Field Productivity records,' which is vague. Missing information about required permissions, error codes, or how crews filters relate to timesheets. The tool name suggests it returns crew-related filter options, but the description does not clarify this.

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% and describes page/per_page well. The description adds minimal value by mentioning pagination control and metadata, but does not explain any filter parameters expected by the tool name.

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 crews filters' but then contradicts by stating it fetches a specific Field Productivity record by identifier. The actual endpoint and parameters suggest a list endpoint, not a specific record retrieval. This inconsistency makes the purpose unclear.

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 vs other timesheet filter tools (e.g., approval status, billable filters). The description does not provide context for selection among siblings or mention when not to use it.

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