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

Annotations already declare readOnly, non-destructive, closed-world, so "Read only; takes no input" is largely redundant. What the description does add beyond structured data is the in_use semantics — a behavioral trait the annotations cannot express — telling the agent that unadopted settings exist and how to react to them, plus the provenance dimension of each value.

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 sentences, front-loaded with the resource and its fields, then the usage instruction, then the in_use caveat, then the read-only note. Every sentence carries information, though the trailing "Read only; takes no input" duplicates the annotation and empty schema and could be dropped without loss.

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?

With no output schema, the description is the only source of return-value information, and it does enumerate the four settings, their provenance values, and the in_use flag — enough to consume the result correctly. It does not describe the exact response shape or whether provenance is a flat field per setting, a minor residual gap for a read-only no-input tool.

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?

Zero parameters, so the baseline of 4 applies; the schema is empty and fully covered. The description correctly states it takes no input, removing any temptation to invent arguments, and usefully spends its words on describing what comes back instead.

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?

Specific verb (get) plus a precisely scoped resource (the regional settings of the organization you are working in), and it enumerates the concrete fields returned: reporting currency, time zone, operating country, communication language, plus provenance (own, inherited, market, platform default). No sibling tool in the list reads tenant-level configuration, so the risk of confusion is low and the boundary is implicitly clear.

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 gives a direct use case — "Use them to show amounts and dates the way the organization works" — and a clear exception path: when in_use is false, the organization has not adopted them, so keep your current defaults. That is actionable guidance an agent can follow without inference. It does not name any alternative tool or prerequisite flow (e.g. after nevent_switch_tenant), which is the only missing piece.

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