list_installed_packages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a listing operation, implying read-only behavior, but doesn't disclose any behavioral traits such as output format, pagination, error handling, or whether it requires specific permissions. The description is minimal and lacks context beyond the basic action.

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 concise and front-loaded with the main purpose in the first sentence, followed by parameter details. There's no wasted text, and it's appropriately sized for a simple tool. However, it could be slightly more structured with clearer separation of sections.

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?

Given the tool has an output schema (which handles return values), no annotations, and low complexity, the description is somewhat complete but lacks context. It covers the basic purpose and parameter, but doesn't provide usage guidelines or behavioral details, leaving gaps for an AI agent to infer correct invocation.

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 schema description coverage is 0%, but the description includes an 'Args' section that explains the 'environment' parameter as 'Name of the Python environment'. This adds meaning beyond the schema's title 'Environment' and default value 'default'. However, it doesn't provide additional details like valid environment names or examples, and there's only one parameter, so the baseline is 4, but the limited info reduces it to 3.

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's purpose with a specific verb ('List') and resource ('installed packages'), and specifies the target ('for a specific Python environment'). However, it doesn't distinguish this tool from its sibling 'list_python_environments', which could be a related listing operation.

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 provides no guidance on when to use this tool versus alternatives like 'list_python_environments' (which lists environments rather than packages) or 'list_directory' (which might list files). There's no mention of prerequisites, typical use cases, or when not to use it.

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