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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds the non-obvious response path (data.data) and the cross-tool dependency on orgId. It says nothing about pagination behavior despite two pagination parameters existing, which is a modest gap.

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?

Three sentences, front-loaded with the action, then the workflow directive, then the downstream rationale. No filler and no repetition of the title.

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?

For a two-optional-parameter read tool with no output schema, the description supplies everything an agent needs: what is returned, where in the payload, and how to use the result. Return values are described inline, which is appropriate without an output schema.

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% with zero required parameters, so the baseline is 3. The description adds no meaning about pageNo or itemsPerPage and never indicates whether the full list is returned by default or must be paged.

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 ('List the DocStar organizations (workspaces)') plus the returned fields (id and name), and explicitly scopes results to organizations the signed-in user belongs to. This is clearly distinguishable from siblings like list_collections or list_collection_pages.

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?

Gives an explicit directive: 'Start every DocStar task here: show the user the organizations and ask which one to use, unless there is only one.' It names the branch condition for skipping the prompt and explains why the tool matters (orgId feeds every other DocStar tool).

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