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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no return format, no side effects, no constraints. A four-word fragment cannot tell an agent what happens when the tool is called.

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?

Brevity here reflects under-specification rather than conciseness; a five-word fragment omits everything an agent needs. There is no structure to evaluate, and no sentence carries actionable content.

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 nine heterogeneous parameters (ref, url, city, feed, host, json, path, zone, query), no annotations, and no output schema, the description is drastically incomplete. Nothing explains what the GPS band output represents or how the unrelated parameters relate to it.

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 description coverage is 100%, so the nine parameters are already documented in the schema and the baseline of 3 applies. The description adds no parameter meaning beyond the schema, but the schema itself does the work.

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?

"GPS second-of-week band" merely expands the acronym in the tool name (gps-sow) into a noun phrase with no verb and no operation described. An agent cannot tell whether this returns a band range, converts a time, or validates input. It does not distinguish itself from siblings like timezone or utc-time.

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 indication of when to use this tool, what inputs are expected, or how it relates to the closely related time tools (timezone, utc-time, iana-zones). Usage must be entirely inferred from the name.

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