demo1_polite_cli

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

The description discloses key behavioral traits: verbosity, long output, and requirement for multiple round-trips. However, with no annotations, it does not cover side effects, safety, or permissions. The disclosure is adequate but not comprehensive.

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 two sentences, but the second sentence adds meta-demo context that is not useful for an agent. It could be more tightly focused on the tool's function without the demo commentary.

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 simple 2-parameter tool, the description lacks details about what each command returns or its behavior. The enum values (status, list-files, deploy-check) are not explained, leaving the agent to guess outputs and effects.

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?

Input schema has 100% coverage with descriptions for both parameters (command enum, verbose boolean). The description adds no additional parameter semantics beyond the schema, so baseline score of 3 is appropriate.

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 states 'Verbose CLI-style helper' but does not clearly state the action performed (e.g., 'runs CLI commands'). It focuses on output characteristics (long text/JSON) and a meta-demo context, making the purpose vague for an AI agent.

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 on when to use this tool vs siblings or alternatives. The description does not mention use cases, prerequisites, or exclusions. The meta-demo language ('before experience') is unhelpful for operational use.

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