wrike_get_space

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it gets a space, without describing the return format, error handling, permissions, or whether the operation is idempotent. The description adds no behavioral context beyond what the tool name and schema already imply.

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, unambiguous sentence that is appropriately front-loaded and free of unnecessary verbiage. It is concise and structurally clear, though it could have been slightly more informative while remaining concise.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is minimally adequate but lacks essential context about the response structure or potential errors. An agent using this tool would not know what to expect as a return value or how to handle non-existent spaces, making it incomplete for robust tool invocation.

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 schema already provides a 100% description coverage for the single parameter (spaceId) with 'Space ID (required)'. The tool description adds no additional semantic value, merely restating that it retrieves by ID. This meets the baseline for high schema coverage but does not enhance parameter understanding.

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 'Get a specific space by ID' uses a specific verb (get) and resource (space), and clearly differentiates from sibling tools like wrike_list_spaces (which lists spaces) and wrike_create_space (which creates a space). It precisely states the operation and scope.

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 provides no guidance on when to use this tool versus alternatives, such as wrike_list_spaces for retrieving multiple spaces or wrike_get_folder for similar resources. There is no mention of prerequisites, exclusions, or recommended context, leaving the agent to infer usage solely from the function name.

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