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

Annotations already declare read-only and idempotent behavior. The description supplements this with concrete parsing behaviors: quoted values, inline comments, export prefix, and escaped sequences, which adds useful context beyond the annotations.

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?

Three sentences: first states purpose, second details parsing capabilities, third gives use cases. Compact, front-loaded, and every sentence adds value.

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 a single parameter, complete annotations, and an output schema, the description covers all necessary context: what it does, how it handles edge cases, and when to use it. No gaps remain.

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 100% and the input parameter is well-described in the schema ('.env file content to parse (e.g. the output of cat .env)'). The description adds little beyond restating that it parses file content, so baseline 3 is appropriate.

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 the verb (Parse) and resource (.env file content), and specifies the output (JSON object). It distinguishes itself from sibling tools like parse_csv and parse_http_headers by focusing on dotenv parsing.

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?

Explicitly lists target contexts: 'CI/CD pipelines, agent config loaders, or when processing dotenv files programmatically.' While it doesn't mention when not to use it or alternatives, the provided contexts offer clear usage guidance.

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