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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value beyond that by declaring the auth scope (demos:read) and enumerating the fields the caller will receive, which is meaningful disclosure for a tool with no output schema. It does not mention result limits or pagination 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?

Two short sentences: the payload specification first, then the hard prerequisite. There is no filler, and the inline gloss on 'demo centers' resolves an ambiguous domain term in a single clause rather than a paragraph.

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, the description correctly steps in and lists the returned fields, including ordering for demo ids, so an agent knows what it gets back. The main remaining gap is any statement about result size, ordering of collections, or pagination, which matters for a workspace-level listing.

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 there is nothing the description needs to disambiguate; the baseline for zero-param tools applies. The description instead spends its words on the response shape, which is a reasonable use of the space.

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 identifies the resource precisely (the workspace's collections) and even defines the domain term 'demo centers' so the agent knows what a collection contains. It stops short of naming a verb or distinguishing this list from nearby list tools such as list_demos or list_brand_kits, but the identity of the resource is unambiguous.

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?

'Requires: demos:read' gives a concrete permission prerequisite, which is genuinely useful for gating a call. However, there is no guidance on when to reach for this versus list_demos or how it pairs with add_to_collection, so the agent must infer its place in the toolset.

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