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

Annotations already declare readOnlyHint=true, and the description adds beyond that: permission accessibility ('Any member may read it'), a semantic guarantee that the metric is only a display default and never affects commissions, and a security warning that CRM field values are untrusted data. These are meaningful behavioral disclosures not present in the annotations.

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 two sentences and front-loaded with the action and resource, followed by a dense but relevant field list and then permission/security context. It is slightly packed but contains no filler; each clause earns its place.

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 getter with one optional parameter and no output schema, the description sufficiently covers the returned fields, permission model, and data-handling caution. Nothing critical is missing, though it could explicitly state the output shape or mention the workspaceId edge case in the description itself.

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 optional workspaceId is fully described in the input schema (100% schema coverage), including when it is required and how search can omit it. The description does not add any parameter-level meaning beyond what the schema already provides, so the baseline score of 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?

The description opens with 'Reads the workspace's commercial defaults' and enumerates the specific fields returned (currency, timezone, forecast horizon, default deal currency, display metric, business type, price periods, setup status). This clearly distinguishes it from the update sibling and other commercial-related tools by establishing both the action and the exact resource scope.

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?

It provides useful context: any member may read it, and the primary display metric never changes commission basis, implying this is not authoritative for commission calculations. However, it does not explicitly name alternative tools or state when-not-to-use conditions, so the agent must infer the selection criteria from the field list and sibling names.

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