Create A New Time And Material Notification

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

The description mentions HTTP 201 on success but provides no additional behavioral details such as failure modes, permission requirements, or side effects. Annotations are minimal (openWorldHint=true), so the description should compensate but does not.

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 three sentences, but contains repetition (e.g., 'Field Productivity records' appears twice) and a redundant final sentence. It is front-loaded with purpose but could be more concise.

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?

With 12 parameters and no output schema, the description lacks essential context such as the meaning of a Time And Material Notification, prerequisites, or the structure of the returned object. This is insufficient for a creation tool.

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?

Input schema has 12 parameters with 100% description coverage, so the schema already documents each parameter. The description adds no extra semantic context beyond the schema, justifying a baseline score of 3.

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 Time And Material Notification for a project, which is a specific resource. However, it also mentions 'Field Productivity records' which introduces slight ambiguity about the category, but overall purpose is clear.

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?

There is no guidance on when to use this tool versus alternatives. The description only says 'Use this to create a new Field Productivity records in Procore,' which implies context but lacks exclusions or comparisons with sibling tools.

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