read_readme

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

No annotations are provided, so the description carries the full disclosure burden. It does tell the agent this is a plain content read of a named file, which is inherently safe and side-effect free, but it says nothing about format, truncation, or whether the file might be absent.

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 short sentence fragment with no wasted words; the file identity and content scope are front-loaded. It is slightly clipped in phrasing but efficient and appropriately sized.

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?

For a zero-parameter, read-only document fetch with no output schema, the description covers what an agent needs: which file and what it contains. Only minor gaps remain, such as the return format or behavior when the file is missing.

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 takes zero parameters, so there is nothing for the description to explain beyond what the empty schema already conveys. Baseline of 4 applies for a parameterless tool.

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?

Names a specific resource (README.md) and a specific verb (Return), plus the content scope ('top-level install + usage'). This implicitly distinguishes it from the many read_* siblings (read_changelog, read_theming, read_agents) that each target a different document, but it never explicitly contrasts itself with those siblings.

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?

Saying the file covers 'top-level install + usage' implies when an agent would want it (initial orientation), but there is no explicit when-to-use guidance and no routing between this and alternatives such as read_llm_txt or read_agents. Usage is inferable, not stated.

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