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

With no annotations, the description must carry behavioral disclosure. It usefully states 'Read-only' and enumerates sensitive returned fields, but does not mention required permissions, whether admin rights are needed to view members/invitations, or any rate/pagination behavior.

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 compact: one sentence listing return contents followed by 'Read-only.' It is front-loaded with the resource and avoids unnecessary prose. The field list is dense but each item adds useful information.

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 zero-parameter, output-schema-less read tool, the description gives a solid inventory of what is returned, including member fields, invitations, and caller admin status. It is incomplete on permissions/usage guidance, but structurally it covers the core return contract an agent needs before calling.

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 the schema coverage is trivially 100% and no parameter semantics are needed. The description correctly avoids discussing inputs and instead focuses on returned data, which is appropriate for a zero-argument tool.

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 that this tool retrieves workspace details: name/owner, members with roles and permissions, pending invitations, and the caller's admin/owner status. It is a specific read operation, though it does not explicitly distinguish itself from siblings like crm_list_workspace_members or get_profile.

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, nor any prerequisites or exclusions. 'Read-only' describes behavior but not usage context, leaving the agent to infer when to call get_workspace instead of member-listing or profile tools.

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