install_environment

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

No annotations are provided, so the description carries the full disclosure burden and fails entirely. It does not state that this is a mutating operation, whether it is reversible, whether it requires elevated permissions, how long it takes, or what side effects it has on existing environments.

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 two-word phrase contains no filler, but it is under-specification rather than conciseness. There is nothing to front-load and no information density to reward.

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?

With no annotations, no output schema, two undocumented required parameters (including a nested object), and zero description content, this definition gives an agent nothing needed to invoke the tool correctly.

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 0% and the description adds no meaning for either parameter. The required "type" string and the nested "config" object are completely unexplained — an agent has no idea what values are valid for "type" or what structure "config" expects.

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?

"Install environment" only restates the tool name with no additional specificity; it does not clarify what an "environment" is (runtime? PHP/Node version? app stack?) or what the install produces. Siblings list_environments and uninstall_environment exist, but the description makes no attempt to distinguish this tool from them.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternatives (uninstall_environment, list_environments). The verb "install" weakly implies a state-changing action, but nothing tells the agent under what circumstances this tool is the correct choice.

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