resolve_assessment

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

No annotations are provided, so description carries full burden. It explains score values and action, but does not disclose effects of multiple calls, error handling, or state requirements. Adequate for a simple update operation.

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?

Two sentences: first states purpose and lists parameters, second gives usage guidance and score mapping. No wasted words, highly efficient.

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?

Covers the primary action, parameter meanings, and usage timing. Missing details on preconditions (e.g., assessment must exist and be pending) but overall sufficient for a simple tool without output schema.

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%, baseline 3. Description adds value by explaining score enum meanings ('right, partially right, wrong') and implying outcome is free text, integrating with the action.

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 states 'Mark an assessment as resolved' with its outcome and score, clearly specifying the action and resource. It differentiates from siblings like log_assessment and list_pending_assessments by indicating this is the finalization step.

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?

Explicitly says 'Call this as soon as the outcome of a prediction is known,' providing clear timing. Does not list alternatives or prerequisites, but the context of assessment lifecycle is implied.

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