Show Timesheet Wbs Code Filters

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

Annotations indicate a read-only, idempotent operation. The description adds pagination details but misrepresents the resource type and does not clarify the actual output (WBS code filters). Behavioral transparency is poor due to inaccurate description.

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 concise but includes incorrect and redundant information. It could be clearer and more accurate.

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 description is fundamentally wrong about the tool's purpose, omitting that it retrieves WBS code filters for timesheets. Without output schema, it fails to set correct expectations.

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%, so the description adds minimal value. It confirms pagination parameters and required company_id, but does not elaborate beyond schema descriptions.

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 title and description suggest this tool shows timesheet WBS code filters, but the text incorrectly describes fetching Field Productivity records. The purpose is ambiguous and inconsistent with the endpoint and title.

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 siblings like list_wbs_codes or other timesheet filters. The description misleadingly suggests fetching Field Productivity records, which is incorrect.

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