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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's added value is the return-content inventory, which matters given there is no output schema, but it says nothing about auth/plan-tier requirements, error behavior for unknown workspace IDs, or whether values are real-time or cached.

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?

One front-loaded sentence with no filler. The unusual unit note ('in millions') is placed inline where it is needed rather than as a trailing caveat.

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 single-parameter read tool the description covers purpose and return contents reasonably well, which is important with no output schema. It falls short on the one required input (workspace_id format/provenance) and on any indication of what happens on failure or for tenants without contracts.

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 description coverage is 0% for the single required parameter workspace_id, so the description carries the full burden. 'For the workspace' only loosely implies the ID's role; it gives no format, source, or how to obtain the ID, leaving the only parameter effectively undocumented.

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?

Uses a specific verb ('Get') and a specific resource ('billing/tenant information for the workspace') and enumerates the returned fields (contract event volume in millions, plan name, org name, owner email). This is enough to distinguish it from a generic sibling such as get_workspace_settings, though it never explicitly contrasts with that sibling.

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 can infer this is the tool for billing/plan/contract questions from the enumerated fields. There is no explicit 'use this when' framing, no exclusions (e.g. vs get_workspace_settings or user_details), and no mention of prerequisites or permissions.

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