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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond the annotations: the store is public, a token is not required, and tokenless clients can read listings as markdown at GET /store. It does not cover pagination or result caps, keeping it at 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?

Roughly three compact sentences with the resource and returned fields front-loaded, then the search alternative, then the auth note. No filler; the markdown-endpoint parenthetical is the only slightly tangential content, though it is relevant context.

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 read-only, zero-required-parameter listing tool with an output-schema-free surface and annotations covering safety, the description supplies the key missing pieces: what fields come back, the sibling to use for searching, and the no-token access path. Only pagination/volume expectations are absent, which is minor.

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 both api_token and convention fully documented in the schema, including the Authorization header interaction. The description adds nothing about parameter syntax or values beyond naming conventions as a listed field, so the baseline 3 applies.

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 names the resource precisely ("Public workspaces (the store)") and states what the listing contains: owner, convention, file count. It implicitly conveys the browse/list action from the name but never uses an explicit verb like "list" or "browse", so it falls just short of a 5 on verb+resource specificity.

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 explicitly routes the agent to the alternative: "Search their contents with query_index(scope='store')", which cleanly separates listing a store from searching inside it. It doesn't spell out a when-not-to-use case beyond that routing, so it's a clear 4 rather than a 5.

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