Creates A New Stand-Alone Transfer.

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

The description goes beyond the annotations by detailing non-idempotency ('calling it again creates another record'), the HTTP 201 response with the new id, and common error payloads (401, 403, 404). It also discloses config defaulting behavior for company_id and project_id. This provides rich behavioral context that annotations alone do not fully convey.

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 longer than typical but every sentence adds value: purpose, item requirements, optional fields, config defaults, non-idempotency, error handling, required params, and API endpoint. It is front-loaded with the core action in the first sentence and structured logically, with no wasteful repetition.

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?

For a complex creation tool with no output schema, the description covers all essential context: inputs, line item constraints, optional fields, defaults, success response (HTTP 201 with new id), and failure modes with common status codes. It also provides the exact API endpoint and domain, making it sufficiently complete for agent invocation.

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 the baseline is 3. The tool description adds meaningful semantics by specifying that line items 'must include a resource guid and quantity,' directly addressing the vague 'items' parameter in the schema. It also clarifies that company_id and project_id default from procore_set_config, which enhances parameter understanding beyond the schema.

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 action: 'Creates a transfer document with the specified header information and line items.' It specifies the resource (transfer document) and provides details about required line item contents, making the purpose unambiguous. The name and title include 'Stand-Alone Transfer,' distinguishing it from the sibling 'creates_a_new_inter_project_transfer' implicitly.

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?

There is no explicit guidance on when to use this tool versus alternatives. While it says 'Required parameters: company_id, project_id' and mentions config defaults, it does not state when to choose this over the inter-project transfer tool or any other related transfer operation. The description implies usage from the action but lacks exclusions or explicit alternative references.

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