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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real value on top: the auth requirement ('Needs the user's Cotlet API key with access to this app') and the permission semantics tied to each role. It does not mention pagination or the exact return shape, keeping it short of a 5.

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 the core purpose, then layered with role and capability detail that earns its place by clarifying what the returned role means. It is slightly long, but no sentence is filler.

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 carries the return-value burden and does so: it explains that each Space comes back with your role. Auth needs are stated. Missing pagination or volume details for a potentially multi-Space list 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?

This tool takes zero parameters, so the baseline is 4. The description correctly implies a no-argument scoping ('your Spaces') and mentions space_id only as an output value to be reused elsewhere, not as an input.

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 ('Lists your Spaces with your role in each') and enumerates the role values returned (owner, admin, moderator, contributor, follower). It is clearly distinguishable from siblings like quora_get_space_stats and quora_list_space_submissions without opening either schema.

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 clear context for why an agent would call it: it supplies the space_id needed by the other Space tools, and it explains the role-based capability model ('only owners... can post'). It does not name a competing alternative tool or an explicit when-not condition, so it stops short of full routing guidance.

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