Create Tax Type

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

Annotations indicate readOnlyHint=false, consistent with creation. The description adds that it returns the created object on HTTP 201, which is helpful. However, it does not disclose permissions, side effects, or other behavioral traits beyond what annotations provide.

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 plus technical details, making it relatively concise. However, there is redundancy (e.g., 'Creates a Tax Type...' and 'Use this to create...' say similar things), and the phrasing could be tighter.

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 covers the basic purpose and required parameters. Given the simple nature of the tool (5 parameters, no output schema) and high schema coverage, it is adequate but lacks differentiation from siblings and explanation of optional parameters.

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%, so baseline is 3. The description explicitly mentions the required parameters (company_id, name) but does not add meaning beyond the schema for optional parameters (description, origin_data, origin_id).

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 'Creates a Tax Type on a given Company', specifying the verb and resource. It also mentions the API group and endpoint, making the purpose unambiguous. However, the phrase 'new Tax records' is slightly imprecise but does not detract from clarity.

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 provides a usage statement ('Use this to create a new Tax records in Procore') and lists required parameters, but it does not offer guidance on when to use this tool versus alternatives like create_tax_code, nor does it specify when not to use it.

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