Lando Exec

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

With no annotations, the description carries the full behavioral burden. It does not disclose that this runs an arbitrary shell command (potentially destructive), whether the Lando app must already be running, whether output or exit status is returned, or any timeout behavior. 'Execute command' is essentially all the agent gets.

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?

It is a single front-loaded sentence with zero waste, but that brevity comes from under-specification rather than tight editing. Nothing is padded, yet nothing useful is added either.

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?

An output schema exists, so return values need not be described, but for an arbitrary command-execution tool with no annotations and zero parameter documentation the description is far too thin. Prerequisites, command scoping, and safety expectations are all missing.

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%, so the description must compensate and it does not: neither the required 'command' string nor 'project_name' (default '.') is explained. The only weak hint is that the verb 'Execute command' loosely maps to the required parameter name, leaving the project scoping argument entirely undefined.

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 names a specific verb (Execute) and resource (command in Lando container), so the agent knows this runs shell commands inside a Lando environment. However, it does nothing to distinguish itself from close siblings like ddev_exec, drush_command, or drush_php_eval, which also execute commands.

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 guidance on when to choose lando_exec over ddev_exec or drush_command, nor any precondition such as 'the Lando environment must be started with lando_start first'. The description states what it does but never when or why to use it.

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