bw_adso_check

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. 'Check' suggests a read-only validation operation, but the description does not state whether it performs a syntax check, a consistency check against metadata, a runtime check, or whether it has side effects. It also does not disclose what happens on failure or what the output looks like.

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, which is concise, but it is under-specified rather than efficiently informative. It is front-loaded with the verb 'Check', but the single phrase does not earn its place because it leaves too much ambiguity.

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 one required parameter, no output schema, and no annotations, the description is incomplete. An agent cannot determine what input to provide, what the tool returns, or how to interpret the result. The sibling context shows many similar ADSO tools, so more detail is needed to avoid mis-selection.

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%, so the description must compensate for the undocumented 'id' parameter. The description only says 'Check ADSO consistency' and does not explain what 'id' refers to (e.g., ADSO name, technical name, UUID) or how it is used. With one required parameter and no schema description, this is a significant gap.

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 'Check ADSO consistency' uses a verb and a resource, but 'consistency' is vague and does not specify what is checked, what result is produced, or how it differs from sibling tools like bw_adso_details, bw_adso_versions, or bw_adso_get_xml. It is not a tautology, but it lacks enough specificity to distinguish it from other ADSO inspection tools.

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 about when to use this tool versus alternatives. The sibling list contains many ADSO-related tools (bw_adso_details, bw_adso_versions, bw_adso_get_xml, bw_adso_transformations, bw_adso_dtps), and the description does not explain what makes 'check' the right choice. The context is implied at best.

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