Show Timesheet Work Classification Filters

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

The description adds some behavioral context: pagination control and metadata. However, it incorrectly describes the return type as 'Field Productivity records' instead of work classification filters, which undermines transparency. Annotations already indicate read-only, so the description adds value but is partially misleading.

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 contains redundant information (e.g., 'Procore API: Project Management > Field Productivity') and a copy-paste error regarding Field Productivity records. It could be more streamlined.

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 fully explain the return structure. It only mentions 'paginated JSON array of Field Productivity records' (inaccurate) and pagination metadata. It doesn't describe what a work classification filter looks like or the fields returned, making 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?

Schema coverage is 100% with parameter descriptions. The description adds context about pagination control and response metadata beyond the schema. It clearly states company_id is required and explains the purpose of page/per_page.

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 inconsistent: it says 'Show timesheet work classification filters' but then claims it fetches 'Field Productivity records'. The name and endpoint clearly indicate it retrieves work classification filters, not Field Productivity records. This contradiction makes the purpose confusing.

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. It does not mention any exclusion criteria or alternative tools for filtering timesheets. Sibling tools include many filter-related endpoints, but the description provides no differentiation.

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