Create Tax Code

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

Annotations are provided (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds context by mentioning required parameters, the API endpoint, and the HTTP 201 success response. 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?

Three sentences containing all necessary information: purpose, required parameters, API reference, and success response. No redundant text; efficient and front-loaded.

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?

No output schema, but the description notes the success HTTP status and that it returns the created object. It specifies required parameters and the domain (Procore Construction Financials). Adequate for a create 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 covers 100% of parameters with descriptions. The description lists required parameters (company_id, code) but adds little beyond the schema. Baseline score due to high schema coverage.

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 Tax Code for a given Company, specifying the resource and action. It also includes the API endpoint and success response, distinguishing it from siblings like list_tax_codes and update_tax_code.

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?

Explicitly states 'Use this to create a new Tax records in Procore,' providing clear usage intent. It does not explicitly mention when not to use, but the creation context is distinct from other operations like update or list, which are present in sibling tools.

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