clawhub_resolve

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

Description mentions returns (matching version and latest version), implying a read operation. No annotations provided, so description bears full burden. Lacks explicit disclosure on side effects, auth requirements, or rate limits. Adequate but not thorough.

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?

Extremely concise with two sentences, no fluff. Purpose and return value are front-loaded. Efficient for an AI agent to parse.

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?

Given simple operation (resolve by hash) and no output schema, description covers core functionality and return value. But missing error conditions, hash format details, or correlation with sibling tools. Somewhat complete but leaves gaps.

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 coverage is 0% as description adds no meaning beyond parameter names. 'Required: slug, hash' is redundant with schema. Does not explain what slug or hash represent, their format, or constraints. Fails to compensate for low schema coverage.

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?

Clearly states the verb 'resolve' and resource 'a version of a skill by content hash'. Distinguishes from siblings like get_version by using hash instead of version ID. Also explains what it returns (matching version and latest version).

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 explicit guidance on when to use this vs alternatives. Implies usage when hash is available, but does not mention when not to use or suggest alternatives like clawhub_get_version for version ID lookup.

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