calculate_zakat

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

No annotations provided, so description carries full burden. It outlines the steps (sums assets, deducts debts, checks nisab threshold) but does not detail exact calculation logic (e.g., how nisab threshold is applied). Adequate but not rich.

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?

Four sentences: purpose, steps, applicability, examples. Front-loaded with clear verb 'Compute'. No wasted words.

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 complexity (11 parameters, no output schema, no annotations), description provides overview and examples but lacks details on output format (e.g., what fields are returned). It mentions 'returns the zakat due' without further structure.

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 100%, so baseline is 3. Description adds minimal extra meaning beyond schema—only mentions asset summing and debt deduction. Parameter behavior is already well-documented in schema.

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?

Description clearly states the tool computes Zakat al-Mal (2.5% annual obligation) and distinguishes itself from siblings like 'calculate_saudi_zakat_citizen' by specifying cross-cutting applicability for any Muslim, any country.

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?

Provides context with 'Cross-cutting — any Muslim, any country' and example queries, but does not explicitly state when not to use this tool versus alternatives like 'calculate_saudi_zakat_citizen'.

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