list_teamspaces

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

The annotation readOnlyHint=true already establishes the safety profile, so the description only needs to add context. It usefully discloses that the response carries ids suitable for reuse, but says nothing about scoping, pagination, or what happens when the workspace parameter is omitted.

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?

A single compact sentence with the key information front-loaded: the resource, then the returned identifier and its downstream use. No filler, though the wording is dense enough to border on cryptic without punctuation.

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-only list tool with the safety profile already covered by annotations and no output schema, the description covers purpose and the return value's use. The undocumented 'workspace' parameter is the main remaining gap an agent would need to resolve before calling it correctly.

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 has one parameter ('workspace') with 0% description coverage, and the description never mentions it. Since the schema cannot carry the burden here, the description should explain whether workspace is required, what its format is, and what an unscoped call returns — it does none of that.

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 ('List') and resource ('document teamspaces'), and clarifies that the useful payload is the teamspaceId, tying it to the sibling tools that consume it. It is clearly distinct from mutation siblings like create_document, though it doesn't explicitly contrast with the other list_* tools.

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 parenthetical 'teamspaceId for list_documents, create_document' tells the agent exactly when this tool's output matters: as a prerequisite lookup before listing or creating documents. There are no explicit exclusions or prerequisites (e.g., permissions), so it falls short of a 5.

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