install

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

With no annotations, the description must disclose behavioral traits. It only says 'Install', not whether installation is additive, destructive, idempotent, or requires specific permissions. Critical details like overwrite behavior or side effects are missing.

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 short (4 words), but under-specified given 23 parameters and no annotations. Conciseness should not come at the cost of essential information; this is too minimal to be effective.

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?

The description is grossly incomplete for a tool with 23 parameters, no annotations, and no output schema. It lacks context on return values, side effects, environment requirements, and how to combine parameters.

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 96%, so baseline is 3. The description adds no parameter-level meaning beyond what the schema already provides. Many parameters have detailed schema descriptions, but the tool description itself is silent on them.

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 'Install an app binary' clearly states the verb and resource. However, it does not explicitly distinguish from sibling tools like 'install-from-source' or 'reinstall', though the binary vs source distinction is implied.

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, prerequisites, or when not to use it. Sibling tools exist but no comparison is made.

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