read_pyproject_toml

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

With no annotations, the description must disclose behavioral traits. It describes the parsing and summarization action and the returned fields, but does not mention error handling, file-not-found behavior, or explicitly confirm that the file is not modified. The read-only nature is implied by the name and 'parse' but not stated.

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 extremely concise, consisting of two short sentences. It front-loads the core purpose in the first sentence and lists expected outputs in the second, with no redundant or irrelevant content.

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 simplicity of the tool and the presence of an output schema, the description covers the essential information an agent needs: what it does, what it returns, and the default file path. It could mention alternatives or edge cases, but for a basic read-only parser this is 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?

Schema description coverage is 100% for the single 'path' parameter, so the schema already documents it. The tool description adds no extra parameter-specific meaning beyond what the schema provides, resulting in a baseline score.

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 verb (parse and summarise) and resource (pyproject.toml). It also lists the specific outputs (project name, version, description, dependencies, tool configurations), which distinguishes it from generic file readers like read_file.

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 a summary of pyproject.toml is needed, but does not explicitly mention alternatives or when not to use this tool. Sibling tools like read_file and read_package_json exist, but no guidance is provided to choose between them.

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