business_mapping_get

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 fails to mention whether the tool is read-only, what effects it has, what it returns, or any side effects. The description is empty of behavioral information.

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 extremely short, but this is under-specification, not conciseness. A single phrase that only repeats the name does not 'earn its place'; it wastes the opportunity to convey useful information. A well-formed conciseness would front-load key facts, which is absent here.

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 the tool's complexity (24 parameters, no output schema, no annotations, and a large set of siblings), the description is wholly inadequate. An agent has no way to know what parameters mean, what the return value is, or how this tool differs from similar ones. Completeness is essentially zero.

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%, meaning the description adds no explanation to any of the 24 parameters. The required parameters (repository_id, target_commit, mapping_id) and optional ones (limit, status, include_candidates, etc.) are entirely undocumented. The description provides no semantic meaning beyond the raw schema.

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 'business mapping get', which is simply the tool name restated. It provides no information about what the tool does, what a 'mapping' is, or what 'get' returns. It is a tautology with no explanatory value.

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 like business_mapping_search, business_mapping_expand, or business_mapping_list. The description offers no context, exclusions, or conditions for selection.

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