Duplicate A Configurable Field Set And Its Custom Fields

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, which align with the description stating it creates a copy. The description adds that it requires specific parameters and references the Procore API endpoint, providing useful behavioral context beyond annotations.

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 concise with four sentences: purpose, usage, required parameters, and API reference. It is front-loaded and efficiently structured, though the API reference adds minor verbosity.

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 no output schema, the description mentions the return status (HTTP 201) and the endpoint. It references required parameters but does not elaborate on the 'include_custom_fields' parameter's effect, though the schema covers that. Overall fairly complete for the tool's complexity.

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% with all four parameters described. The description repeats which parameters are required but adds no new semantic meaning beyond what the schema already provides. Baseline 3 for high coverage is appropriate.

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 'Duplicate a Configurable Field Set and its custom fields' and identifies the specific resource. It mentions creating a copy and returning HTTP 201, but does not explicitly differentiate from other duplicate/clone tools among many siblings.

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 duplicate an existing Custom - Configurable Tools as a new record' but provides no guidance on when not to use it or what alternatives exist. No exclusions or context for decision-making.

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