get_r_company_agent_credentials_mapping_id

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'Retrieve' and shows the GET method, implying read-only, but does not mention auth requirements, error behavior (e.g., 404 when mapping not found), rate limits, or pagination specifics. The reference to 'filters and pagination' hints at behavior but lacks detail.

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 two sentences, front-loaded with the core action and endpoint, then concise parameter guidance. Every sentence earns its place, though the second sentence is a terse list that could be slightly clearer about which parameters are optional.

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 values need no explanation EB. The description covers the basic call signature and parameter roles, but given the tool's moderate complexity and the large sibling set, it could mention that this is the single-item variant of a two-endpoint CRUD pair, and clarify how to specify the ID (e.g., as a string 'id' key in path_params). It is adequate but not comprehensive.

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 does assign meaning to three of four parameters: path_params hold route IDs, query holds filters/pagination, headers hold request headers. However, it does not name specific query keys or describe the body parameter (likely irrelevant for GET), leaving the agent to guess the exact filter/pagination syntax.

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 the action 'Retrieve agent credential mapping' and identifies the exact API endpoint with a `{id}` placeholder, making clear it fetches a single mapping by ID. It does not explicitly contrast with the sibling `get_r_company_agent_credentials_mapping` (which lists mappings), but the ID suffix and endpoint template imply the distinction.

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 tips ('route IDs in path_params, filters and pagination in query, and any required request headers in headers') but provides no guidance on when to use this tool versus alternatives, such as the list endpoint or the POST/PATCH variants. No explicit exclusions or prerequisites are mentioned.

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