business_mapping_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses nothing: no side effects, no return behavior, no permissions, no edge cases. The description is empty of any behavioral content.

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?

While the description is extremely short, this is under-specification rather than conciseness. There is no useful information, so it fails to earn any 'efficiency' credit. A description should be concise but informative; this is simply absent.

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?

For a tool with 10 parameters, no annotations, and no output schema, this description is grossly incomplete. An agent has no idea what inputs are required, in what format, or what the tool returns. It cannot be invoked correctly or even selected appropriately.

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 meaning to any of the 10 parameters (3 required). There is no explanation of what repository_id, target_commit, context_id, or any other field represents beyond their names. The agent cannot infer parameter semantics.

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 exactly 'business mapping list', which merely restates the tool name. It does not state a verb, a resource, or any distinguishing scope. An agent cannot tell what this tool does beyond the literal words, and it does not differentiate from siblings like business_mapping_search or business_mapping_get.

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?

No guidance is given on when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or exclusions. The agent is left entirely to inference from the name and schema.

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