delete_d_company_agent_credentials_mapping_id

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

No annotations are present, so the description carries the full burden of disclosing behavior. It states the delete operation but does not mention that deletion is destructive, irreversible, or may impact related data. It also omits any permission requirements, idempotency, or side effects. This is a significant gap for a delete tool.

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 brief and front-loaded with the primary action, followed by a direct reference to the endpoint. It avoids unnecessary words, making it easy to skim. However, it could be more structured by separating the action from parameter placement, but it is acceptably concise.

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?

While an output schema exists (per context signals), the description does not explain what the mapping is, when deletion is appropriate, or what the response will look like. It also introduces 'filters and pagination in query' which is atypical for a delete and unexplained. Given the destructive nature and the zero-coverage schema, the description is incomplete for an agent to confidently invoke the tool.

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%, and the schema itself uses generic objects for body, query, headers, and path_params with no specific properties. The description mentions 'route IDs' in path_params but is vague (singular vs plural) and does not clarify what filters or pagination are relevant for a delete, nor what headers may be required. It fails to provide enough meaning for an agent to correctly populate parameters.

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 the action ('Delete agent credential mapping') and identifies the specific resource via the endpoint path. It distinguishes this tool from its get/post/patch siblings for the same mapping resource, so an agent can select it unambiguously.

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 provides some guidance on where parameters go (path_params, query, headers) but does not explain when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., existence of the mapping) nor contrasts with update or create operations. The usage context is implied rather than explicit.

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