Add Wage Override

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that it creates a new record and returns HTTP 201, which aligns with annotations. No contradictions, but no additional behavioral details beyond what annotations imply.

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 four sentences with redundancy: 'A successful response returns the new Wage Override UUID' and 'Creates a new Resource Planning records and returns the created object on success.' 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?

Given 4 parameters and no output schema, the description covers the basic action and required params. However, it lacks usage context, error handling, or prerequisites (e.g., must have access to the project). Annotations help but description doesn't fully compensate.

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 lists required parameters but adds no meaning beyond what the schema already provides. No explanation of rate format or job title UUID source.

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 ('Add a Wage Override for a specific Job Title in a Project') and the verb 'add' is specific. However, it includes redundant statements about returning the UUID and creating a record, which detracts slightly. It distinguishes from siblings like delete_wage_override.

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 says 'Use this to create a new Resource Planning records in Procore,' which is vague and does not specify when to use this tool versus alternatives (e.g., delete_wage_override). No when-not or alternative guidance is provided.

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