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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It does add useful behavior: 'Only published collections are listed' and 'nothing is generated on demand', which clarifies the read-only, non-dynamic nature. However, it omits details like pagination, ordering, or return format, which would be needed for a fully transparent list operation. The extra behavioral notes justify a solid 3 but not a 4.

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 efficiently written: a front-loaded definition, a brief context sentence, a clear usage sentence with alternatives, and a practical note about slugs. Every sentence earns its place without fluff or repetition, making it easy to scan.

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?

Given there is no output schema, the description compensates by explaining the collection concept, mentioning the slug for get_collection, and clarifying published-only behavior. It lacks explicit return-field details or pagination, but for a browse tool the core information is present. A small gap keeps it from a 5.

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 fully documents the optional 'type' filter with its enum and meaning. The description adds no extra parameter semantics beyond that, which fits the baseline 3 for high coverage. It does hint at themed sets but does not map directly to the enum values.

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 clear verb-and-resource statement: 'List Vectree's curated collections' and specifies the content type (hand-assembled groups of diagrams). It differentiates from siblings by naming alternatives like search_diagrams and search_learning_paths, so an agent can confidently choose this tool for browsing.

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 description explicitly states when to use this tool ('to browse', 'to answer what is on Vectree?', 'to find a themed set of diagrams') and when not to use it ('When the user already has a topic in mind, use search_diagrams; when they want an ordered syllabus, use search_learning_paths'). It also tells the agent to pass the slug to get_collection for interior diagrams, covering downstream usage.

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