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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it discloses the return content (verdict, main scholarly views, halal alternatives) and that it also handles single ingredients and E-numbers, which is not derivable from the schema.

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?

Front-loaded with the core action, then a compact parenthetical enumeration of coverage domains, ending with return content. The domain list is long but each item earns its place by communicating scope. No filler sentences.

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 free-text Q&A tool with no output schema, the description adequately explains what it answers and what it returns. However, in a family with a dozen overlapping halal tools, it omits any guidance on scope boundaries or limits, leaving the agent unable to route 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?

There is a single parameter with 100% schema description coverage, and the schema itself supplies the example question format ('Is a credit card halal?'). The description adds no additional syntax or constraint detail, so the baseline 3 applies.

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?

States a clear verb+resource: answer any 'is it halal' question, and enumerates the covered domains (money, crypto, medicine, food/drink, everyday life) plus ingredient/E-number recognition. The purpose is unmistakable, but it does not differentiate itself from the many dedicated siblings (halalornot_check_crypto, halalornot_check_medicine, halalornot_check_ingredients), so an agent cannot tell when this catch-all is preferred.

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 when-to-use or when-not-to-use guidance is provided, and the description never names or defers to the more specific sibling tools. The broad domain list actively overlaps with halalornot_check_crypto, halalornot_check_medicine, and halalornot_check_ingredients, leaving routing entirely to inference.

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