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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it discloses what each returned item contains (summary, page, downloadable model file, and an Open-in-Blueprint-Modeler link when available), which is critical since there is no output schema.

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 packs the resource and the return payload without filler. The trailing 'where there is one' qualifier is slightly awkward but adds a real nuance about optional links.

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 no output schema, the description usefully enumerates the fields returned, and annotations cover the safety semantics. It is complete enough to call correctly, though it omits any hint of ordering, pagination, or volume of diagrams.

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?

The schema accepts zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; no parameter syntax or meaning is needed or missing.

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 ('List the reference diagrams') and even scopes the content to CSDM models drawn in Blueprint Modeler. It does not explicitly distinguish itself from siblings, but get_page/list_toolbox/search_site are far enough in kind that confusion is unlikely.

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: a parameterless enumerator of all diagrams. There is no statement of when to reach for this versus a search or page-fetch tool, and no prerequisites or exclusions are given.

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