Inspect conda env

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the named-vs-path scoping dimension but says nothing about return format, whether packages include versions, or how an unreachable/remote env is handled — with annotations doing the heavy lifting, this is adequate but thin.

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?

A single front-loaded sentence with zero filler; the operation and its target are stated before any qualifier.

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?

With 4 parameters, no output schema, and only 50% schema coverage, the definition is minimal. It never says what a package entry looks like (name only, name+version, channel) or whether profile/project scope the inspection, leaving the agent to discover the result shape by calling it.

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 only 50% (envName and envPath carry regex patterns but no prose). The description compensates by clarifying that the two selectors are a name or a path, signaling they are alternate ways to target the same env rather than independent options — meaningful semantics not present in 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?

States a specific verb+resource: 'List packages' scoped to 'a named or path-based conda env'. This implicitly separates it from ris_list_conda_envs (which enumerates envs, not their contents), but it never names or explicitly contrasts that sibling, so an agent must infer the boundary.

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 when-to-use guidance, no statement of prerequisites (e.g., that the env must exist or be reachable), and no guidance on choosing between the two env selectors. The word 'or' hints the selectors are alternatives, but no usage rule is stated.

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