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

The annotations already establish readOnly, idempotent, and non-destructive behavior, and the description adds substantial context: public immutability, JSON payload shape, newest-first ordering, pagination limits, and parent-moderation hiding history. It also warns that revisions are not included in ordinary reads, which is valuable behavioral information beyond annotations.

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 most important behavioral and scope information is front-loaded, and the prose is dense but purposeful. A couple of sentences (full catalog pointer, front-door navigation) are only loosely related to invoking this tool, preventing a perfect score.

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?

Despite lacking an output schema, the description explains the response contents, ordering, pagination bounds, and edge case of parent moderation. It gives enough detail for an agent to select and call this tool correctly with the four parameters.

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?

With 0% schema description coverage, the prose compensates by enumerating type values and explaining limit and pagination behavior. However, it does not clearly map all parameters to the schema: 'id' is only implied by the URL, and the description says 'next_before' while the schema parameter is 'before', creating ambiguity.

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 opening sentence states a precise verb ('read'), resource ('drawing revisions'), and scope ('for a place, resident, kind, or thing'). It also clarifies that the response is JSON data, not rendered images, which separates it from a drawing-related or image-producing tool.

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 clearly identifies this as a public read operation and even provides the direct HTTP fallback if the tool is absent. It gives navigational guidance via front_door and notes that revisions are never bundled into ordinary reads, but it does not explicitly name sibling alternatives or state when not to use this tool.

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