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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond that: the response is HTML and it reflects the piece's current state rather than a prior version. It says nothing about size limits, sanitization, or what happens if the name does not match.

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 with the resource and return format front-loaded and no filler. Nothing could be removed without losing information.

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 two-parameter read tool with full schema coverage and complete read-only annotations, the description covers what is needed to call it, and usefully discloses that the payload is raw HTML since there is no output schema. It stops just short of addressing how a piece name is matched or how large a document may be.

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 both parameters carry descriptive text, including an example of the human-visible piece name. The description only implies that "name" selects the single piece being read and adds no format, matching, or case-sensitivity guidance beyond the schema.

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?

"Read one piece's HTML" gives a specific verb and resource, and uniquely states the return format (HTML) plus the freshness qualifier "as it is now". It does not explicitly name a sibling to distinguish itself from ads_look_at or ads_list_pieces, which keeps it out of the top band.

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?

Usage is only implied: an agent can infer this is for inspecting a piece's current markup, presumably before an ads_edit_piece or to verify an ads_write_piece result. There is no explicit when-to-use, no mention of when to prefer ads_look_at, and no stated prerequisites.

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