python_env_info

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

Annotations indicate read-only. The description adds that it 'requires local installation', which is behavioral context not captured by annotations. This aligns with readOnlyHint and provides useful extra info.

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: first states what it does, second gives usage and prerequisite. No wasted words, and the key information is front-loaded.

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?

Despite no output schema, the description covers return values (path, version, package list) and intended use. For a simple, read-only tool with no parameters, it is fully adequate.

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 tool has 0 parameters, so baseline is 4. The description is not required to add parameter info, and it correctly omits any.

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 'Get Python executable path, version, and pip package list', which is a specific verb+resource. It distinguishes from all sibling tools that are Rosetta-related, so no ambiguity.

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 explicitly says to use for diagnosing environment issues or verifying package installations, and notes a prerequisite (requires local installation). It doesn't state when not to use, but given the tool's narrow focus and sibling context, this is sufficient.

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