arcane_list_environments

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

No annotations are provided, so the description carries the full burden. It mentions listing and optional filtering, but does not disclose whether this is a read-only operation, what the response format is, or whether there is any pagination. Given no output schema, the agent lacks information about return structure.

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 a single concise sentence that is front-loaded with the core action ('List all environments') and immediately states the optional filter. It contains no filler or redundant information.

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?

The tool is simple (one optional parameter, no output schema), and the description covers the primary action and filter. However, it omits details about the return payload (e.g., does it return full environment objects or just names?) and any potential limitations. For a list tool, this is sufficient for basic use but leaves room for assumptions.

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?

The input schema already fully describes the search parameter as 'Search term to filter environments by name or description' (100% coverage). The description merely echoes 'filter by search term' without adding extra syntax, default behavior, or edge cases, so it adds no additional value beyond the 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 clearly states the tool lists all environments, with an optional search filter. This is a specific verb+resource combination ('List all environments') that distinguishes it from sibling tools like arcane_get_environment, which presumably retrieves a single environment.

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 implies usage when you need to see all environments, optionally filtered. However, it does not explicitly mention alternatives or when not to use it. There is no comparison to arcane_get_environment or creation tools, so guidance is implied rather than explicit.

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