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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful context beyond that by specifying the workspace is 'approved' and that the response includes the membership role, though it does not disclose error behavior or authorization failure handling.

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, focused sentence with no filler. It front-loads the core purpose and return content, which is appropriately sized for a one-parameter, read-only getter.

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 tool with one well-documented parameter and strong annotations, the description covers the essential return value and authorization scope. It falls slightly short of 5 because it does not mention potential error conditions or explicitly connect usage to the authorization flow beyond the schema's parameter description.

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 single parameter workspaceSlug has 100% schema description coverage, including its pattern, length limits, and authorization context. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate because the schema carries the weight.

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 uses a specific verb ('Return') and resource ('workspace'), and adds meaningful scope ('approved') and return content ('current membership role'). This clearly distinguishes it from sibling tools like list_workspaces, which would return a collection rather than a single workspace with role information.

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?

Usage is only implied: an agent would use this when it needs the approved workspace and the current membership role. There is no explicit statement of when not to use it or which alternatives exist, but the resource and context are clear enough to infer the basic trigger.

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