get_r_integration_company_mappings_id

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

With no annotations, the description carries the full behavioral disclosure burden. It clearly identifies this as a GET/retrieve operation, implying read-only behavior. However, it does not mention authentication requirements, error/404 behavior, or what 'required request headers' actually are, leaving those aspects opaque.

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 compact and front-loaded with the endpoint, and the second sentence earns its place by explaining parameter placement. Minor wording awkwardness ('Retrieve company mapping Calls') prevents a perfect score, but there is no fluff.

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?

An output schema exists, so return-value details are not required. However, given zero annotation coverage and zero schema descriptions, the description leaves important gaps: the exact route ID parameter, available filters and pagination keys, header requirements, and the purpose of the `body` parameter are all unclear. It is minimally viable but not complete for an agent to call confidently.

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% and all four parameters are generic object types, so the description must add meaning. It helpfully maps path_params to route IDs, query to filters/pagination, and headers to required headers. But it never names the concrete parameters (e.g., the `id` itself), says 'route IDs' plural for a single `{id}` endpoint, and does not address the `body` parameter at all.

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 states a concrete action ('Retrieve company mapping') and gives the exact endpoint `GET /r/integration/company_mappings/{id}`. The `{id}` suffix and singular 'mapping' distinguish it from the collection-level sibling `get_r_integration_company_mappings`, though it does not explicitly name that sibling.

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 the collection endpoint or other integration mapping tools. The description tells the agent how to supply parameters but never says 'use this when you have a company mapping ID' or contrasts it with `get_r_integration_company_mappings`.

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