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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that by characterizing the payload: preview, source brief, free DXF download, and a link to draw a similar one, plus that the output is unretouched genuine output. It does not mention pagination or the default/max item count.

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 front-loaded sentence that starts with the usage trigger and then packs in scope, source, and per-item contents. No filler, no repetition of the title.

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?

With an output schema present, return values need not be spelled out, and the annotations fully cover the safety profile. The only residual gap is guidance on the 'limit' parameter and whether results are paginated, which is minor for a two-optional-param listing tool.

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 50%: 'query' is documented in the schema (with examples like 'townhouse', '3 bedrooms') while 'limit' is only constrained by min/max/default. The description mentions neither parameter, so it adds no meaning beyond the schema — adequate but not compensating for the coverage gap.

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 gives a specific verb and resource — 'Lists published drawings from the Plan Chat CAD studio' — plus the nature of the content ('real, unretouched output'). It implicitly distinguishes itself from list_my_cad_drawings via 'community/published', but never names that sibling outright.

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 opening 'Use this when the user wants to see what the AI drafter draws, or examples of AI-made CAD floor plans' gives a concrete trigger tied to user intent. There are no explicit exclusions or named alternatives, so an agent must infer that 'my drawings' routes elsewhere.

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