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 all entries return in one call, enumerates the row fields including conditional nameCount/valueCount, and clarifies that copying is not automatic. It does not explicitly label the operation read-only or confirm no side effects, but the implication is strong.

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 purpose, then return contents, then the usage/alternative. Every sentence adds information, though the field enumeration could be tightened. No filler or redundancy.

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?

No output schema exists, so the description justifiably explains the return shape in detail (name, sector, complexity, features, status, description, nameCount, valueCount). Combined with the usage and sibling routing, an agent has everything needed to call it correctly.

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 tool takes zero parameters, so the baseline of 4 applies. There is no parameter syntax to clarify and the description appropriately focuses on return contents instead.

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 and resource: browsing the shared Azquo library of example/demo databases. It distinguishes itself from sibling list_* tools by scoping to demo/example catalogues and names copy_from_library as the separate write 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 ('answer questions like is there an example with setup sheets?'), tells the agent there is no separate search endpoint, and clearly delineates the copy step as a distinct, explicitly-requested action routed to copy_from_library.

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