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

With no annotations, the description carries the full burden. It usefully discloses that the server is paid, the auth mode, and the exact price ($0.003 per call via x402/MPP), which is meaningful behavioral context an agent needs. But it says nothing about input validation ranges, error behavior, or supported date bounds.

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 summary sentence is front-loaded and clear, but the bulk is metadata noise: origin URL, hostname, brand, provider aliases, family key, endpoint, repeated keyword lines, and largely redundant use cases. This bloats a one-line conversion tool's description with low-value 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?

For a simple 3-param conversion tool with no output schema it covers the core operation, direction, and payment requirement. The gaps are the undocumented parameter ranges/format and lack of any statement about the return value's shape, though the use-case examples partly convey the output.

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 0% and the three required params (year, month, day) have no descriptions. The description only implies format via the example 'convert 2026-03-21 to 1405-01-01', leaving accepted ranges, negative/zero handling, and input format (numeric vs string) undocumented.

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 summary states a specific verb+resource with an unambiguous direction: 'Convert a Gregorian date to the Iranian Jalali (Solar Hijri) calendar.' The direction inherently distinguishes it from the sibling jalali_to_gregorian without needing to name it.

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 concrete usage context ('Use for any Iranian date, holiday or deadline') and lists four use cases covering today's date, a specific date, a deadline, and a birth date. However, it never states when NOT to use it or explicitly names jalali_to_gregorian as the alternative for the reverse direction.

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