business_mapping_confirm

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

No annotations are provided, so the description must disclose behavior. It does not state whether the tool is a read, mutation, or validation action, what side effects occur, what authorization is needed, or what the response looks like. Zero behavioral context is given.

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 (three words) but this is under-specification, not effective conciseness. There is no useful content to be structured or front-loaded; it fails to convey the tool's purpose.

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 24 parameters, no output schema, and no annotations, the description is completely inadequate. An agent cannot determine valid parameter combinations, expected values, or the operation's semantics. Essential details are entirely absent.

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?

With schema description coverage at 0% and 24 parameters (7 required), the description adds no meaning to any parameter. Even the required parameters like 'repository_id', 'target_commit', 'mapping_id', 'expected_version', 'status', 'actor', and 'evidence_refs' are 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 a verbatim restatement of the tool name ('business mapping confirm'), providing no verb+resource specification, no scope, and no distinction from numerous siblings like 'semantic_confirm', 'confirm', or 'knowledge_confirm'. It is a pure 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 statement of when to use this tool versus alternatives, no exclusions, and no mention of prerequisites. Given over 80 sibling tools including multiple confirm-like operations, the agent receives no routing guidance whatsoever.

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