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

Annotations already cover readOnly, idempotent and non-destructive, so the safety profile is settled. The description goes further by disclosing a data quirk that no annotation could convey: monetary values elsewhere are unlabelled bare numbers, and enable_floorplans is not enforced because floorplans exist on every plan. It stops short of stating auth/permission requirements, but the added context is substantive.

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?

Front-loaded with the returned field list, then the critical cross-tool usage rule, then the module-emptiness note. It is longer than most definitions but nearly every clause carries actionable information; the closing module sentence is the weakest earner.

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 burden of describing the return payload and does so field by field. Combined with the currency caveat and module semantics, an agent has everything needed to call and interpret this tool correctly.

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 per the rubric the baseline is 4. The description's field list describes return values rather than inputs, which is useful but not a parameter-semantics contribution.

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 and resource ('Get this organization's display settings') and enumerates exactly what is returned: currency_code (ISO 4217), timezone, date_format, company_name, org_category, and enabled modules. No sibling tool covers this resource, so the agent can distinguish it immediately.

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 an explicit when-to-use rule with rationale: call before presenting any monetary amount, because costs/budgets/replacement values from every other tool are bare numbers with no currency attached. It also names a second use case (distinguishing an empty module from an unavailable one). Nothing is left to inference.

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