islamhouse_categories_tree

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not state that the operation is read-only, safe, or whether it requires any permissions or has side effects. The description is too minimal to inform the agent about 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 concise sentence that directly states the tool's purpose. It is front-loaded and contains no fluff. However, it could be expanded slightly to include usage guidance without becoming verbose.

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 of returning a complete hierarchy tree and the absence of an output schema, the description is too sparse. It does not explain the structure of the tree, pagination (if any), or how to interpret the response, leaving the agent under-informed.

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 input schema has 100% coverage for the single 'language' parameter with a basic description ('Language code'). The tool description does not add any additional meaning or constraints (e.g., format, default, allowed values). According to the rubric, baseline is 3, and no extra value was provided.

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 it retrieves the complete categories hierarchy tree in IslamHouse, using a specific verb ('Get') and resource ('categories hierarchy tree'). While the name implies a tree structure, it does not explicitly differentiate from sibling tools like 'islamhouse_child_categories' or 'islamhouse_sub_categories', though the word 'tree' suggests a full hierarchy rather than partial lists.

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 guidance is provided on when to use this tool versus siblings like 'islamhouse_all_categories' or 'islamhouse_child_categories'. There is no mention of prerequisites, context, or alternatives, leaving the agent without decision support.

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