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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real context: model keys are redacted from the response, the required credential scope, and the 403 refusal for unclaimed workspaces. That goes well beyond what the annotations convey.

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 scope statement and the field list are front-loaded, and the auth/prerequisite sentences follow cleanly. The middle field enumeration is long but each item is informative rather than filler; a slightly tighter grouping of the field list would earn a 5.

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?

There is no output schema, so the description carries the return-shape burden itself — and it does, listing the returned settings and the one redaction (model keys). Access prerequisites and the 403 edge case cover the remaining risk of an incorrect call.

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 there is nothing for the description to disambiguate; baseline 4 applies. No misleading param hints are given.

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+resource ('Read your workspace settings') and enumerates the exact fields returned (company name, tax id, currency, invoice prefix, tax registrations, sales playbook). This is clearly distinguishable from the mutating sibling update_workspace_settings and from other get_* settings tools such as get_billing_settings or get_analyst_settings.

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?

Gives concrete conditions for when the call will succeed: a Last Price credential with workspace settings read scope and a claimed workspace, with the explicit failure mode (403) for sandbox keys from self-registration. It does not explicitly contrast with update_workspace_settings, but the read/update split is unambiguous from the name.

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