Bulk Update Time And Material Timecards

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

The description adds that only supplied fields are changed (partial update) and returns the modified object. Annotations provide readOnlyHint=false, which is consistent. However, it lacks details on error behavior, authentication, or rate limits.

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 with no fluff, front-loading the main action. Could be slightly tighter but adequately sized.

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 tool with 2 parameters and no output schema, the description covers purpose, partial update, return value, required params, API category, and endpoint. Could mention error handling or batch size limits.

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 descriptions for both parameters. The description repeats required parameters but does not add new meaning beyond what the schema already provides.

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 the tool performs a bulk update of time and material timecards, distinguishing it from create/delete/list siblings. It specifies verb 'bulk update' and resource 'Time and material timecards'.

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 indicates when to use: to update existing Field Productivity records with partial updates. It does not explicitly state when not to use or mention alternatives, but the context of siblings makes it clear.

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