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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the 'only reads' sentence largely restates them. The description still adds value by disclosing the ownership filter (only workspaces the user owns) and the UUID form of the identifier, which annotations do not convey. Pagination, ordering and what fields come back are unstated.

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?

Three short sentences, zero filler. The core purpose is front-loaded, followed by the practical routing advice and the scope guard. Nothing repeats the tool name or wastes tokens.

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 no-argument, read-only list tool whose safety profile is fully covered by annotations, the description is nearly complete: it explains why to call it and what identifier it yields. It could mention what else a workspace record contains (e.g., name) to set expectations around the return shape, which has no output schema.

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 tool takes zero parameters, so there is nothing for the schema to document and no description burden is created. Baseline 4 applies; the note that workspace_id is a UUID is a helpful return-value hint rather than a parameter detail.

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 with scope: 'List the workspaces the user owns.' The closing clause ('does not create, rename or share') explicitly separates it from create_workspace, so an agent can distinguish it from siblings without opening any 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 an explicit trigger — call this to obtain the workspace_id needed before create_conversation, list_memories, list_documents or get_company_context — and an explicit exclusion (no create/rename/share). The when and when-not are both stated, naming the concrete downstream tools.

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