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

With no annotations, the description carries the full burden and does well: it discloses that fetching the page is unnecessary, that the graph can be walked via the Linked/Related diagram slugs, and that unknown slugs silently yield no diagram. It does not mention rate limits, auth requirements, or size limits on large diagrams, so it falls short of complete.

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?

Front-loaded with the return payload, then usage, then constraints across three short paragraphs. The sentence explaining what Vectree is provides orientation but is the most expendable part; otherwise every sentence earns its place.

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 and no annotations, the description must cover return values and constraints, and it does: payload contents, graph-walk slugs, and the public/on-demand limitation. Missing only operational details such as diagram size limits or failure signalling for bad slugs.

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 defines the single slug parameter and its format (baseline 3). The description adds meaning beyond the schema by explaining that slugs appearing in the 'Linked diagrams' and 'Related diagrams' sections are valid inputs to this same tool, which is not stated in the 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?

States a specific verb (Fetch) and resource (one Vectree diagram) and enumerates exactly what is returned: labelled nodes with explanations, animated walkthrough, image URLs, and links. This is clearly distinguishable from sibling read tools like get_collection or get_learning_path.

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 states when to use it ('after search_diagrams to read a result in depth, or whenever you already know a Vectree slug') and names the sibling search_diagrams as the entry point. It also gives a when-not condition: only public, already-generated diagrams exist and nothing is generated on demand, so an unknown slug returns nothing rather than an error.

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