calculate_zakat

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the need for gold/silver price per gram to determine nisab, but does not explain what happens when these are omitted, how the calculation is performed, or what the output represents. This is insufficient for a financial calculation tool.

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 concise, consisting of two short sentences that front-load the main purpose. Every sentence adds useful information, with no redundant or filler 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?

Given the tool has 5 parameters, no output schema, and no annotations, the description is incomplete. It does not specify the return value format, the calculation methodology, or how optional prices interact with different wealth types. A user would need significant external knowledge to use this tool confidently.

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 0%, so the description must compensate. It adds valuable context by listing allowed wealth_type values and highlighting the role of gold/silver price per gram. However, it does not explain the meaning of 'amount' (is it total wealth?) or the currency parameter, leaving ambiguity in parameter semantics.

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's purpose: 'Calculate Zakat due on wealth.' It lists the wealth types (cash, gold, silver, trade_goods), making the scope explicit. However, it does not explicitly distinguish itself from sibling tools like calculate_gold_nisab and calculate_silver_nisab, which could handle gold/silver-specific calculations.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It implies usage for wealth generally, but does not state conditions like 'use for mixed wealth' or exclude cases where gold/silver nisab calculators are more appropriate. There's also no mention of prerequisites beyond supplying prices.

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