coeus_verify_solution

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

No annotations are provided, so the description carries the full burden, and it only restates the verification intent. It does not disclose whether the tool invokes a model, what kind of result is returned (pass/fail, score, report), or whether there are side effects.

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?

A single sentence with no filler and the action front-loaded. It is efficient, though barely structured enough for a five-parameter tool.

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?

With no annotations, an output schema, or usage guidance, a statement of purpose alone is not enough for a five-parameter tool. The agent cannot tell what it will receive back, which inputs matter for verification semantics, or how this tool compares to related verification/review siblings.

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 100%, so the schema already labels all five parameters, but those labels are minimal ('Model', 'Context', 'Solution', etc.). The description adds relational meaning for three parameters by saying verification is against requirements, test criteria, and context, though it does not clarify how 'model' participates.

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 names a specific action ('Verify') and an object ('a solution'), plus the criteria it applies ('requirements, test criteria, and context'), so an agent knows the core function. It does not explicitly differentiate this tool from siblings like coeus_multi_model_verify or coeus_review, so it falls short of the top score.

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 when-to-use guidance, no prerequisites, and no mention of when to prefer another tool. The description simply states the operation, leaving the agent to infer appropriate conditions for calling it.

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