get_analytics_group_workspaces

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds genuinely new behavioral facts: pagination, the Enterprise gating requirement, and the concrete 403 failure mode on non-Enterprise plans. This is exactly the context annotations cannot express.

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 tight sentences: return shape first, then usage, then gating. The opening sentence is dense with field names but front-loads the most useful information. No filler.

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 33-param read-only tool with a 100% covered schema and an output schema, the description still supplies the two things structured fields omit: the Enterprise gate with its 403 outcome and the drill-down routing. Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so all 33 parameters are already documented by the schema, and the description adds no per-parameter syntax or default details. The only parameter mention (workspace_slug) is framed as a drill-down handoff rather than semantics for this call, so baseline 3 applies.

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 (Get) and resource (paginated per-workspace breakdown) and enumerates the returned shape (total_groups, group_count, is_quota_exceeded, workspaces array with workspace_slug/request count/cost). The 'per-workspace' scope implicitly distinguishes it from the get_analytics_group_users/models/providers siblings, so an agent can route correctly.

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?

Explicitly names the use case ('org-wide chargeback or comparing workspaces') and points to the drill-down alternative ('pass workspace_slug to other analytics tools'). The alternative is described generically rather than by name, so routing is clear but not maximally precise.

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