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

With no annotations, the description carries the full burden and handles it well: it states that nothing is generated on demand and an unknown slug simply has no diagram, clarifying the failure mode. It also discloses the read-only nature of the fetch and gives the practical consequence (no need to fetch the page). A minor omission is the lack of an exact error/return convention for non-existent diagrams, though 'simply has no diagram' covers the core behavior.

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 compact and starts with the main action, followed by context, usage, and constraints. Every sentence contributes meaning, though 'returns the complete text of one of them' slightly restates the opening 'full content' phrase. This is a minor redundancy in an otherwise efficient description.

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, so the description must stand in for return-value documentation—it does, listing labelled nodes, explanations, image URLs, and outgoing links. It also covers chaining, public-only access, and the unknown-slug case, making it complete for an agent deciding whether and how to call the tool. Nothing critical is missing.

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 input schema already documents the single `slug` parameter with concrete examples (search_diagrams result or URL path segment), so the baseline is 3. The description adds one useful detail—that `Linked diagrams` and `Related diagrams` produce slugs that can be passed straight back—but otherwise does not need to add more because the schema is comprehensive. Score is at baseline.

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 opens with a specific verb ('Fetch') and resource ('full content of one Vectree diagram'), then enumerates exactly what is returned (labelled nodes, explanations, image URLs, links). This clearly differentiates it from the collection/learning-path siblings by focusing on diagram content, even without naming them explicitly.

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?

It gives explicit when-to-use instructions: 'Use it after search_diagrams to read a result in depth, or whenever you already know a Vectree slug.' It also explains a follow-up pattern (passing linked/related slugs) and warns that only public, already-generated diagrams can be fetched. It does not explicitly mention the sibling collection/learning-path tools as alternatives, which is the only gap.

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