Bulk Create Materials

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

The description adds meaningful behavioral context beyond the annotations: it specifies the HTTP method and endpoint (POST /rest/v1.0/...), notes that partial failures can occur, and indicates the response is the created collection (HTTP 201). The annotations (readOnlyHint=false, destructiveHint=false) are consistent with a creation operation. 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 (4 short sentences) and front-loaded with the core purpose. It efficiently conveys the primary use case, endpoint, important behavior (partial failures), and required parameters. No 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?

Given the tool's complexity (bulk create, potential partial failures), the description covers the key aspects: what it does, when to use, how to handle failures, and the result. However, it omits details like rate limits, authentication scope, or maximum batch size, which could be important for a bulk operation. Still, it is reasonably complete for the purpose.

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?

With 100% schema coverage, the base is 3. The description reiterates that both parameters are required and clarifies that project_id is a URL path parameter and time_and_material_materials is a JSON body field. This adds minimal value beyond the schema, as the schema already describes each parameter's type and location. No further details on the structure of the array items or examples.

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 action ('Bulk create Material entries'), the resource ('materials' in Field Productivity), and the outcome (returns collection with HTTP 201). It explicitly contrasts with single-create tools (sibling 'create_material') by specifying 'with one request' and 'many records'. The title and tool name reinforce this.

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 directly advises to use this tool when creating many Field Productivity records in a single request, implying it's for bulk operations. It also warns about partial failures and instructs to check each item's status. While it doesn't explicitly say 'use create_material for single records', the sibling tool name and context make this clear. Missing explicit when-not-to-use statement.

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