Retrieve workspace

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

Beyond annotations (readOnly, idempotent, not destructive), the description adds behavioral details: workspace IDs start with 'tea-', user IDs default to user's workspace, and the underlying API call is GET /owners/{ownerId}. This provides useful context beyond what annotations offer.

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 three sentences long, with the first two slightly redundant. It is front-loaded with the core purpose and adds specific details efficiently. Very little waste, though it could combine the first two sentences.

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 read operation with one parameter, no output schema, and comprehensive annotations, the description covers ID formats and special behavior. It lacks details about the response structure, but that is partially mitigated by the lack of output schema. Overall, it provides adequate context.

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 input schema describes ownerId as 'The ID of the user or team' (100% coverage), so baseline is 3. The description adds value by specifying ID prefix rules ('tea-' for workspace, 'own-' for user) and the special behavior for user IDs, which are not in the schema.

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 clearly states the tool retrieves a workspace, specifies that workspace IDs start with 'tea-' and user IDs start with 'own-', and explains the behavior for user IDs. This clearly differentiates it from sibling tools that retrieve other resources.

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 gives context on ID formats and the API endpoint, but does not explicitly state when to use this tool over alternatives like render_retrieve_service or render_retrieve_postgres. Usage is implied for workspace retrieval without exclusion guidance.

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