Resolve ONES Requirement

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

The description 'Resolve' suggests a state-changing write operation, but the annotations declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating a safe read-only operation. This is a direct contradiction, making the description misleading. No additional behavioral details (e.g., side effects, auth requirements) are provided.

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 concise with two sentences. The first sentence clearly states the action and identifier types. The second sentence provides usage guidance. No redundant or unnecessary information.

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?

Despite having an output schema (not shown), the description is incomplete due to the annotation contradiction and lack of clarity on what 'resolve' means. It does not explain the tool's effect or when it is appropriate to use. For a tool that appears to mutate state, this is a significant gap.

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?

The schema has one parameter 'ref' with no description (0% coverage). The description adds meaning by saying it can be a number, task id, or task URL, but does not specify format or constraints beyond the schema's minLength. This is helpful but insufficient for fully understanding the parameter.

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 'Resolve an ONES requirement by number, task id, or task URL', giving the action and resource. However, the term 'resolve' is ambiguous (could mean mark as resolved or another operation) and the readOnlyHint annotation contradicts the implication of a write operation. It does distinguish from siblings by mentioning '_by_ref' tools, but lacks clarity on the exact semantics.

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 includes 'Prefer *_by_ref tools for normal workflow reads', which provides some guidance on when not to use this tool. However, it does not explicitly state when to use this tool or clarify its purpose versus the alternative tools. The contradiction with annotations further confuses usage.

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