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

Annotations already establish that this is a read-only, idempotent, non-destructive, open-world tool. The description adds meaningful behavioral context beyond annotations: how to handle last_reviewed, what to do when truncated is true, and the legal-information disclaimer.

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 four compact sentences with no wasted text, and the core purpose is front-loaded before the handling instructions. Each sentence carries operational value for correct invocation or interpretation.

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 rich schema coverage, existing output schema, and annotations, the description is complete enough for an agent to call and use the tool correctly. It covers pagination continuation, review-date handling, and the legal disclaimer without redundantly restating schema details.

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%, so the schema already documents url, offset, and max_chars. The description reinforces the offset continuation semantics but does not mention max_chars, so it adds only modest value beyond the structured 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?

The description states a specific verb and resource: "Read one PropertyList guide." The word "one" clearly distinguishes this tool from the sibling search_guides tool, so an agent can identify its role without opening the schema.

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 gives clear usage context and explicitly tells the agent how to continue when a page is truncated via offset and next_offset. It does not explicitly name search_guides as the alternative for discovering guides, but the schema's url description supplies that routing context.

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