list_calculation_methods

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns exactly 10 methods and mentions the inclusion of Fajr/Isha angles, which gives basic expectations. However, it does not clarify if the output is static, how it behaves on error, or other behavioral traits.

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 a single sentence that is perfectly concise and front-loaded with the main action. Every word adds value, and there is no extraneous information.

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?

Given the tool has no parameters and no output schema, the description adequately explains what is returned (list of 10 methods with angles). However, it could be slightly more complete by noting if the list includes names, descriptions, or other fields, or any ordering. Still, it is sufficient for a simple listing 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?

There are no parameters, so the description does not need to add parameter information. The schema is empty, and coverage is 100% by default. A score of 4 reflects the baseline for parameterless tools.

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 clearly states the tool lists exactly 10 supported prayer time calculation methods with their Fajr/Isha angles. It is specific about the verb (list), resource (calculation methods), and scope (all 10, with angles), distinguishing it from sibling tools like calculate_fasting_times or get_prayer_times.

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?

No explicit when-to-use or when-not-to-use guidance is provided. However, for a simple parameterless listing tool, the context is implied: it is used to retrieve the list of calculation methods. No alternatives are mentioned, but the sibling tools are clearly focused on different tasks.

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