business_mapping_expand

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

No annotations are given, and the description says nothing about side effects, read/write behavior, permissions, or what operations are performed. For a tool with 24 parameters and no annotations, this is a total absence of behavioral disclosure.

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 extremely short, but this is under-specification, not conciseness. There is no front-loaded information, no sentence structure, and the entire description is a single redundant phrase that provides zero value.

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?

Given 24 parameters, 3 required, no output schema, and no annotations, the description is completely inadequate. An agent would have no idea what the tool does, how to call it, or what the required parameters mean.

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 description adds no information about any of the 24 parameters. The description only repeats the tool name, leaving every parameter's meaning completely unexplained.

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 is just the name repeated ('business mapping expand'). It provides no verb, resource, or action, and does not differentiate from siblings like business_mapping_search or business_mapping_get. This is a tautology.

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 use this tool versus alternatives. No context, conditions, or exclusions are provided. With over 80 sibling tools, the lack of any routing info is a severe gap.

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