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

No annotations are provided, so the description carries full behavioral burden. It discloses that only published collections are returned, that unknown slugs yield no collection, and that entries can be in a 'still generating' state. It does not explicitly state that this is a read-only fetch, but the verb 'Fetch' strongly implies it, and the described behavior is otherwise thorough.

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 a few sentences but every sentence earns its place: the first sentence states the core function, the second explains what a collection is, and the subsequent sentences give actionable context about usage and edge cases. It is organized into clear paragraphs and is not padded.

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?

There is no output schema, but the description explains exactly what is returned (description, diagrams in curated order) and how to proceed with each entry via `get_diagram`. It also covers edge cases like 'still generating' and unknown slugs. An agent has everything needed to call this tool correctly and interpret the result.

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 fully documents the `slug` parameter. The description adds usage context (e.g., where to get the slug) but essentially repeats the schema's guidance about list_collections results and URL segments. It does not introduce meaning beyond the schema, so the baseline 3 is appropriate.

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 uses a specific verb ('Fetch') and a precise resource ('one Vectree collection'), then spells out what it returns: description and diagrams in curated order. It also distinguishes itself from siblings like `get_diagram` and `list_collections`, so an agent can select it correctly without opening schemas.

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?

Explicitly says 'Use it after list_collections, or whenever you already know a collection slug', and gives a clear exclusion: skip entries marked 'still generating'. It also notes that only published collections can be fetched and that nothing is generated on demand, which shapes call expectations.

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