business_mapping_reverse

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

No annotations are provided, and the description offers no behavioral disclosure—no side effects, permissions, reversibility, or return behavior. With zero annotation coverage, the description carries full burden and fails entirely.

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 text is very short, which is usually good, but here it is under-specified to the point of being a near-tautology. Conciseness requires conveying essential information efficiently; this conveys none, so it earns a low score for structure.

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?

With 24 parameters, no output schema, and no annotations, a useful description is critical. This tool has none, making it completely inadequate for correct invocation without external knowledge.

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% across 24 parameters, and the description adds no meaning to any parameter. The schema itself provides minimal hints (e.g., enums), but the description offers nothing to compensate for the large gap.

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 'business mapping reverse' merely repeats the tool name without any verb or resource explanation. It does not clarify what 'reverse' means or what operation is performed, so an agent cannot discern the purpose from this text alone.

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 absolutely no guidance on when to use this tool versus its many siblings like business_mapping_search or business_mapping_get. No context, prerequisites, or exclusions are provided.

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