business_mappings_validate

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

No annotations are provided, and the description carries no behavioral information. It does not disclose side effects, safety profile, read/write nature, error conditions, or any operational details. The single repeating line adds zero transparency.

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 brief, but this is under-specification rather than effective conciseness. It has no structure or front-loaded information; it merely echoes the tool name, providing no value to the agent.

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 6 parameters, required nested objects, and no output schema, the description is grossly incomplete. It fails to explain validation rules, return format, or even the basic intent. An agent cannot reliably invoke this tool based on this definition.

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 gives no explanation of any parameter. While the schema reveals 'context' has repository_id and target_commit, and 'mappings' is an array, the purpose and format of these are completely unexplained. The description adds no meaning beyond field names.

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 literally the tool name repeated: 'business mappings validate'. It does not state what the tool does, what validation means in this context, or what outcome the agent can expect. This is a classic tautology with no verb or resource elaboration, and there is no differentiation from the many sibling validators.

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 the many other validators (e.g., edge_validate, node_semantic_validate, business_candidates_validate). No scenario, prerequisites, or conditions are provided. An agent would have to guess which validator fits its task.

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