get_r_integration_company_mappings

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It identifies the HTTP method (GET through the URL) implying a read operation, and states it retrieves mappings. However, it omits any details about authentication requirements, error handling, pagination behavior, or the response structure. For a GET endpoint, this is a minimal disclosure that doesn't fully inform the agent about potential side effects or prerequisites.

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 extremely concise: two sentences with no filler. The core action 'Retrieve company mappings' is front-loaded, and the following sentence provides parameter guidance efficiently. Every word serves a purpose, making it ideal for an agent to quickly parse.

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?

Although an output schema exists (so return values are covered), the lack of annotations means the description must explain behavior and usage context. It fails to mention authentication requirements, rate limits, or any conditional behavior. It also doesn't clarify the relationship to the ID-specific mapping endpoint or when one is preferred. For a relatively simple GET tool, this is incomplete given the minimal supporting structured data.

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 0%, so the description must compensate. It adds meaning to three of the four parameters: path_params for route IDs, query for filters and pagination, headers for required header values. It does not mention the body parameter, leaving that unexplained. While this partial coverage is helpful, it doesn't fully compensate for the schema's lack of descriptions, especially for the body parameter which is present but undocumented.

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 it retrieves company mappings, using a verb and a specific resource. It doesn't explicitly differentiate from sibling tools like get_r_integration_company_mappings_id, but the name itself is distinct enough. Without naming alternatives, it's clear but lacks explicit sibling contrast.

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 parameter placement guidance (path_params for route IDs, query for filters/pagination, headers for required headers) but provides no guidance on when to use this tool versus alternatives. There's no mention of scenarios, preconditions, or why one would choose this over the ID-specific or write variants.

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