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

Beyond the annotations, the description discloses two non-obvious behaviors: held (uncommitted) changes are included in the returned content, and large files are truncated with a note explaining how to page. That is exactly the extra context annotations cannot convey. It stops short of saying what happens on a missing path or what the truncation limit is.

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 short sentences with the scope, the unit returned, and the paging caveat front-loaded; no filler. The fragmentary construction ('On one site of the account, named in site.') is slightly cryptic but never padded.

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 read-only tool with no output schema, the description covers truncation and held-changes semantics, which are the critical behaviors. It omits error behavior for a bad path, encoding assumptions, and how 'theme' relates to 'path', leaving real gaps for an agent composing the call.

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 only 20%, so only 'site' is documented, and the description merely repeats that the site is 'named in site'. 'whole or by a line range' maps to start_line/end_line and gives them meaning, but 'theme' and 'path' (path format, relative root) remain undocumented in both schema and description.

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 identifies the resource precisely: one text file of a theme on a named site, returned whole or by line range. It implicitly distinguishes from list_theme_files (single file vs. listing) and from write/edit_theme_file by describing a retrieval. The verb is only implied ('One text file of the theme...'), which keeps it short of a 5.

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?

There is no statement of when to use this instead of siblings such as list_theme_files, search_theme, or read_site_page, and no prerequisites or exclusions are given. The line-range hint is a capability, not usage guidance.

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