Uruchom komende w katalogu site

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

Beyond the annotations, the description discloses important behavior: it waits by default, returns output, has a one-minute maximum wait, and executes on a production server. This meaningfully supplements the annotations and gives the agent a clear safety picture.

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?

Three sentences with no wasted words: the action is front-loaded, examples are included, behavior is stated, and the production-safety warning is placed at the end. Every sentence earns its place.

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?

For a four-parameter tool with no output schema, this description is complete: it explains where the command runs, what it does, how waiting and output work, and why caution is needed. The absence of an output schema is compensated by the explicit statement that output is returned, capped at one minute.

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 100%, so the schema already documents all parameters. The description adds extra meaning by clarifying runtime behavior (default wait, one-minute timeout) and providing realistic command examples, which helps the agent understand expected command syntax beyond the bare schema.

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 uses a specific verb and resource: 'Uruchamia komende powloki w katalogu site' (runs a shell command in the site directory). Examples like 'php artisan migrate --force' and 'php artisan cache:clear' make the intent unambiguous and help distinguish it from deployment or server-management siblings.

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?

The description gives clear operational context: commands run in the site directory on a production server, and the agent is told to check the command before running it. It does not explicitly name alternatives or when-not-to-use conditions, but for a generic shell command tool the production warning is strong context.

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