list_environments

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

No annotations, but description discloses it searches directories, returns file paths, and is a read-only list operation. It doesn't mention error handling or permissions, but for a simple list tool this is adequate.

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?

Two sentences, front-loaded with purpose, no wasted words. Efficient and clear.

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?

Covers what, where, and output format. Missing details on absolute/relative paths, but sufficient for an agent to use correctly alongside sibling tools.

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?

No parameters in schema, so description adds meaning by explaining the search scope and return value, which is valuable beyond the empty 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?

Description clearly states it lists all local Mockoon environment files and returns file paths. The verb 'list' and resource 'environment files' are specific, and the mention of passing to 'start_mock' distinguishes it from sibling tools like create_environment or start_server.

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?

Provides context on where it searches (default directory and MOCKOON_DATA_DIRS), implying when to use it. No explicit when-not or alternatives, but sibling differentiation is clear through naming.

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