semantic_confirm

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals nothing about side effects, whether confirmation is idempotent, whether it writes state, or what failure conditions exist. For an operation that presumably modifies confirmation state, this is a complete gap. However, there is no contradiction with annotations since none are present.

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 technically brief (two words), but it is under-specification rather than conciseness. There is no substance to evaluate for structure or front-loading—it is simply a placeholder that repeats the tool name.

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 7 parameters, a nested object, no annotations, no output schema, and a semantic confirmation purpose that must be distinguished from at least three similarly named siblings, the description is completely inadequate. An agent has no way to call this tool correctly.

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 there are 7 parameters including required 4 (context, semantic_id, confirmed_by, expected_version), plus a nested object. The description provides zero insight into what parameters mean, how they relate, or why expected_version is required. A nested context object with repository_id and target_commit adds complexity that the description fails to clarify.

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 'semantic confirm', which is a tautology of the tool name. It provides no verb, no resource, no scope, and no differentiation from similar siblings like 'confirm', 'knowledge_confirm', or 'business_mapping_confirm'. An agent cannot determine what this tool actually does.

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?

The description contains no guidance on when to use this tool versus any of the many confirmation-related siblings. Given the presence of several similarly named tools (business_mapping_confirm, knowledge_confirm, semantic_term_search), this ambiguity is critical and unaddressed.

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