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

No annotations are provided, and the description says nothing about side effects, safety, return values, or what happens to the 9 accepted parameters. It does not even state whether the tool performs a read-only calculation or modifies state, leaving the agent completely blind to its behavior.

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?

At three words, it is short, but this is under-specification rather than effective conciseness. There is no useful front-loading, no structure, and no information that earns the agent's attention beyond a vague concept.

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 9 optional parameters, no required fields, no output schema, and no annotations, the description should provide the context the agent needs to call the tool safely. It provides none of that, so the agent cannot determine which inputs are relevant or what a successful response would be.

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 description coverage is 100%, so the baseline is 3 even though the tool description itself adds no parameter meaning. However, 'Julian day number' does not help map any of the 9 generic parameters (ref, url, city, feed, host, json, path, zone, query) to the tool's operation, and none of them obviously carries a date input.

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 'Julian day number' restates the tool name as a noun phrase rather than describing a concrete operation. It does not say whether the tool converts a date, fetches today's number, or validates a value, and it fails to differentiate itself from siblings like utc-time, timezone, or normalize-url.

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 at all on when to use this tool versus an alternative. The description offers no triggers, conditions, prerequisites, or exclusions, so an agent cannot decide when julian-day is the right tool.

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