Create Company Vendor Business Register

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

The description discloses that the tool creates a new record and returns the created object on success (HTTP 201), which adds value beyond the annotations. Annotations indicate it is not read-only or destructive, and the description aligns with that, providing additional detail about the response.

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 reasonably concise with five sentences. It front-loads the core purpose and then adds details about parameters, the API, and the response. There is no fluff, but it could be slightly more compact.

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 there is no output schema, the description adequately covers the return behavior (created object with HTTP 201) and the API endpoint. For a simple create tool, it is fairly complete, though it does not mention error handling or duplicate scenarios.

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 the baseline is 3. The description lists the required parameters but does not add new meaning beyond what the schema already provides. It mentions that 'identifier' ignores spaces and dashes, which is already in the schema description.

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 uses specific verbs ('Create', 'associated with') and clearly identifies the resource ('Business Register' for a 'Vendor'). It distinguishes this tool from siblings by focusing on a specific entity type, and it is not a tautology.

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 states 'Use this to create a new Directory records in Procore' but does not provide guidance on when to use this tool over alternatives (e.g., create_company_vendor, create_company_vendor_insurance). No exclusions or when-not-to-use information is given.

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