Bulk Upsert LOV Codes

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

Annotations already disclose readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds valuable context: defaulting of IDs, return value ('Returns the modified bulk upsert LOV code on success'), and common failure statuses (401, 403, 404). This goes beyond annotation basics, though it could mention idempotency explicitly (but annotation covers it).

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 moderately detailed and well-packed into a few sentences. It front-loads the purpose and includes useful endpoint, error, and default information. It is not overly verbose, though it could be tightened slightly by separating the API reference from the behavioral guidance.

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 tool is a bulk operation, but the input schema and description do not specify how to supply the LOV codes to be upserted. This is a critical gap that prevents correct invocation. Error handling and defaults are described, but the essential request body is missing, leaving the description incomplete for practical use.

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?

The schema has 100% coverage for company_id, project_id, and Accept-Language, but the core payload for bulk upserting LOV codes is entirely absent. The description does not explain how to pass the actual codes to be upserted, making it impossible to correctly invoke the tool based on the provided information. The defaulting note for company_id/project_id is helpful but does not compensate for the missing bulk data parameter.

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 tool's function: 'Creates or updates project naming standard LOV code mappings in bulk.' It specifies the resource (project naming standard LOV codes) and distinguishes from sibling tools like bulk_upsert_lov_codes_company by explicitly mentioning 'project' and providing the project-scoped endpoint.

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 gives clear guidance: 'Prefer this over repeated single-record calls when handling many bulk upsert LOV codes at once.' It also clarifies default behavior for company_id/project_id from procore_set_config. However, it does not explicitly mention when to use the company-level variant instead, leaving a small gap in alternative selection.

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