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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description's job is to add return-shape context. It does that well: current offset, abbreviation, DST observance, all clock changes in the year with local before/after times, and the next change. The ambiguity note about IST/CST and disclosure of which zone was resolved is genuinely useful behavioral detail.

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 use case, then the return contents, then the ambiguity caveat — a logical order with no filler. The middle sentence is long but each clause maps to a distinct returned field.

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 carries the burden of explaining returns and does so field by field, and annotations cover the safety profile. It stops short of describing error behavior for unresolvable places or out-of-range years, which is the only meaningful gap for a two-parameter lookup 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?

Schema coverage is 100%, so both parameters are already documented in the schema, and the description adds only a little: it implies `place` tolerates abbreviations and that `year` scopes the clock-change listing. It adds no format or edge-case detail (e.g. what happens with an ambiguous abbreviation or a year with no DST) beyond the schema.

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 states a specific resource (zone offset/abbreviation/DST/clock changes) and enumerates exactly what is returned, including the next change. It is clear enough to separate from generic time tools, though it never names the sibling tools (meridian_now, meridian_convert_time) it should be distinguished from.

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 explicit triggering questions ("what is the UTC offset of X", "does X observe daylight saving", "when do the clocks change"), which is strong when-to-use guidance. It lacks any when-not-to-use or named alternative, so an agent must infer the boundary against meridian_convert_time and meridian_now.

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