wrike_list_spaces

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

With no annotations, the description carries the burden. 'List' implies read-only and safe, and 'all spaces in the account' provides scope. However, it does not disclose default behavior regarding archived spaces (e.g., whether archived are excluded unless withArchived=true) or pagination, which are important for a listing tool.

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?

The description is a single, front-loaded sentence with no wasted words. It is appropriately sized for a simple list tool.

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 simple list tool with one well-documented parameter, the description is largely complete. No output schema exists, but 'List all spaces' implies a list return. Minor gap: does not mention default archived filtering or pagination, but these are not critical for basic usage.

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 coverage is 100%: the lone parameter withArchived has a clear description ('Include archived spaces'). The tool description adds no extra parameter context, so 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 'List all spaces in the account' clearly states the verb (list) and resource (spaces) with a specific scope (all in the account), distinguishing it from sibling tools like wrike_get_space (single space) and wrike_create_space.

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?

The description clearly indicates this is for retrieving a collection of spaces, which is distinct from get/update/delete operations. However, it does not explicitly exclude alternatives like get_space for single-space retrieval, though the name and description imply that.

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