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

Annotations already establish readOnlyHint and idempotentHint, so safety is covered. The description adds meaningful behavioral context beyond the annotations: only manifest-declared files are readable, and a paid theme's source requires an active license, which tells the agent about potential call failures. This is valuable, non-redundant information.

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 with no filler. The primary action is front-loaded, and the license caveat is separated clearly. It does not repeat schema or annotation information unnecessarily.

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 low-complexity read tool with rich annotations and full schema coverage, the description is complete enough. It identifies the allowed file categories, the manifest restriction, and the license prerequisite, which are the main operational concerns. The return format is obvious from the verb 'Read,' and no output schema exists to require elaboration.

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 covers 100% of the parameters with descriptions, and the tool description does not add substantive meaning beyond what the schema already provides. The mention of 'manifest-declared' aligns with the file parameter's schema description but does not enrich it further. Given full schema coverage, 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?

The description uses the specific verb 'Read' and defines the resource as 'one manifest-declared component, page, theme.css, AGENTS.md, or README.md file,' leaving no ambiguity about what the tool does. The enumerated file types clearly distinguish this file-reading tool from siblings like get_theme or download_theme, even though they are not named. It avoids tautology and states observable scope.

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 clear context for when the tool is appropriate: it reads only manifest-declared files, and paid themes require an active license, which is a concrete prerequisite. However, it does not explicitly name sibling tools or state when to prefer them over this tool, so cross-tool routing is left partly to inference. This is just shy of fully explicit guidance.

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