List Timecard Time Types

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 value by explaining pagination behavior (page, per_page) and that the response includes pagination metadata. No contradictions.

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 with 6 sentences that are well-structured: purpose first, then usage, return format, pagination control, required parameter, API reference. No verbose filler.

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?

For a simple list tool with 3 parameters, the description covers purpose, use cases, pagination details, required parameter, and API endpoint. It lacks output schema but notes pagination metadata. No significant gaps.

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 baseline is 3. The description adds context for page and per_page (control pagination) but the schema already describes them. 'Required parameters: company_id' repeats schema. Minimal added semantic value.

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 clearly states it returns a list of Timecard Time Types for a company. The verb 'Return a list' and the resource are explicit. However, it inconsistently refers to 'Field Productivity records' which may not match the resource name, slightly reducing clarity.

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 provides some usage guidance: 'Use this to enumerate Field Productivity records when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not explicitly mention when not to use or offer alternative tools, which is moderate guidance.

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