post_w_integration_company_mappings

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only repeats the mutation intent ('Create') already implied by the name and endpoint. It does not mention authentication needs, side effects, idempotency, required headers, or response behavior—significant gaps for a write operation.

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 short sentences with no filler; the purpose is front-loaded and the parameter placement instructions are direct. It is concise, though slightly repetitive in structure ('Provide X in Y' repeated), which is acceptable but not perfectly polished.

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 POST tool with an effectively empty schema and no annotations, the description is under-specified: it lacks the shape of the required body payload, the meaning of route IDs, authentication requirements, and any clarification of 'filters' or 'pagination' parameters. The presence of an output schema helps return-value expectations but does not compensate for the missing request-side detail.

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 0%, so the description must compensate. It adds useful high-level guidance by mapping parameter categories: route IDs to path_params, filters and pagination to query, headers to headers, and payload to body. However, it does not provide any concrete field names, formats, or examples, leaving the actual parameter structure largely unspecified.

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?

States a specific verb and resource ('Create company mapping') and explicitly names the HTTP endpoint (`POST /w/integration/company_mappings`), which distinguishes it from sibling patch/get/delete operations. However, it does not define what a 'company mapping' is, leaving some ambiguity about the exact resource semantics.

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 implies this tool is for creation via the verb 'Create' and the POST method, but it provides no explicit when-to-use guidance or alternatives (e.g., 'use patch_w_integration_company_mappings for updates'). It gives placement instructions for parameters but no conditions, exclusions, or context for choosing this tool over siblings.

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