Draft Create

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

Annotations declare readOnlyHint=false, consistent with a create operation. The description adds that it returns the created object on success (HTTP 201) and provides the endpoint. However, it does not disclose behavioral details like draft state implications, performance, or idempotency, which are not covered by annotations.

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 verbose, mixing deprecation notice, alternative endpoints, API details, and purpose. It could be more concise by separating deprecation info or front-loading the core action. The structure is cluttered.

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 explains the output (created object on success) and required parameter, but lacks details on what 'draft create' means, any post-creation flow, or constraints on timecard_entries array content. Given the complexity of bulk creation and absence of output schema, the description is moderately complete.

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 description coverage is 100% for all 3 parameters. The description only reinforces project_id as required and does not add meaning beyond what the schema already provides. Per guidelines, baseline 3 is appropriate when schema covers parameters adequately.

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 creates a Timesheet and Timecard Entries in bulk as a 'draft create'. It identifies the resource (Field Productivity records) and verb (create). However, the deprecation notice and alternative endpoints slightly cloud the purpose and may cause confusion about whether this tool is still intended for use.

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 explicitly marks the tool as DEPRECATED and provides alternative endpoints for separate creates, implying when not to use it. However, it lacks explicit guidance on when to use this tool vs. alternatives, leaving ambiguity about the recommended usage scenario.

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