get_r_company_agent_credentials_mapping

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

No annotations are present, so the description carries the full disclosure burden. It reveals the HTTP method is GET, implying a read operation, but it does not discuss auth requirements, default pagination, scoping, or what the mapping represents. This is only slightly more transparent than having no description at all.

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?

Two short sentences, front-loaded with the purpose and the endpoint, with no filler. The phrase 'any required request headers in headers' is slightly tautological but does not bloat the description.

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?

Despite the output schema covering the response, an agent cannot reliably construct a correct request: the specific route IDs, pagination/filter keys, and required headers are not identified, and the body parameter is unaddressed. For a generic four-parameter wrapper with no annotations, this is a meaningful gap.

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?

The schema properties are generic catch-all objects with no descriptions (0% coverage), so the description's mapping of path_params to route IDs, query to filters/pagination, and headers to required headers adds real meaning. However, 'route IDs' is vague and the body parameter is never mentioned, so the compensation is incomplete.

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 opens with a specific verb and resource ('Retrieve agent credentials mapping') and names the exact HTTP endpoint, so an agent knows what operation this performs. It does not explicitly say 'list all mappings' or contrast itself with the _id sibling, so it falls short of full sibling differentiation.

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 guidance on when to choose this tool over get_r_company_agent_credentials_mapping_id or the related credential/agent tools. The only usage hint is where to put path, query, and header values, which is invocation mechanics rather than decision guidance.

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