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

With no annotations provided, the description carries the entire burden of behavioral disclosure, yet it reveals only a nominal fact. It does not state that the tool is read-only, what it returns, why 10 optional parameters exist, or how they affect the call.

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 extremely short, but brevity here is under-specification, not economy. A 10-parameter tool with no annotations or output schema requires a substantive description; a five-word phrase is not appropriate.

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?

The tool has no annotations, no output schema, 10 optional parameters, and 30 siblings. The description explains none of the return contract, the role of the parameters, or how this tool relates to utc-time, timezone, or calc-eval. It is far from complete for an agent to call safely.

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 schema provides 100% parameter description coverage, including explicit behavior such as 'discarded after the shape check' and 'no disk access'. The description adds no additional parameter meaning, so the high-coverage baseline 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 'UTC ISO quarter 1-4' reads as a label rather than a functional statement. It identifies a topic (ISO quarter) and a range (1-4) but never states what action the tool performs on any resource, nor does it distinguish itself from siblings like utc-time or timezone.

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?

There is no guidance about when to invoke this tool, what inputs it expects, or which alternatives might be more appropriate. An agent cannot tell whether this returns the current quarter, validates a quarter, or formats a timestamp.

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