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

With empty annotations, the description carries the full burden for behavioral disclosure, but it only states that it 'returns' metadata, implying a read-only operation. It does not mention whether it performs any network calls, whether it has side effects, or what happens to the many input parameters, leaving significant behavioral ambiguity.

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 a single, concise sentence that front-loads the core verb and object. It contains no redundant words, though its brevity is insufficient for a tool with 43 parameters, which is more a completeness concern than a conciseness one.

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 the tool's complexity (43 parameters, no output schema, no annotations), the description is far from complete. It explains the high-level output but fails to define 'portable install metadata', clarify inputs, or cover any edge cases, leaving agents without enough context to invoke it reliably.

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 only 33%, and the description adds no parameter semantics whatsoever. It does not mention any of the 43 parameters or explain how inputs relate to the returned metadata, failing to compensate for the schema's low 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?

The description clearly states the action ('Return portable install metadata') and specifies the target consumers (OpenClaw, Hermes-style, Codex/CLI, MCP clients, Bankr-style), which gives the tool a distinct identity. However, it does not explicitly differentiate from sibling tools like install_skill or download_skill, so it falls short of a 5.

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 provided on when to use this tool versus alternatives such as install_skill, download_skill, or get_playbook. The description implies it is relevant for installing into specific agent frameworks, but there is no explicit context, prerequisites, or exclusion criteria.

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