fanar_poem

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 usefully discloses a prerequisite ('Requires Fanar-Diwan on the key'), which is real context beyond the schema, but says nothing about output format, length, streaming, or failure behavior for a generative 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?

Two short sentences, front-loaded with the core action, with no filler. It is appropriately sized, though the second sentence reads as a prerequisite note rather than description.

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 generative tool with no annotations, no output schema, and an undocumented prompt parameter, the description leaves too much unstated: no return-value expectations, no prompt guidance, and no usage context beyond the model requirement.

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 single 'prompt' parameter has 0% schema description coverage and the description adds no guidance on what the prompt should contain (theme, meter, length, style). An agent gets no help constructing a valid input.

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 specific verb ('Compose') and resource ('Arabic poetry in the classical tradition'), which clearly distinguishes it from generic siblings like fanar_chat or fanar_translate. It names the backing model (Fanar-Diwan) but does not explicitly contrast against alternative tools.

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?

There is no guidance on when to choose this tool over fanar_chat for poetry, nor any exclusions or prerequisites beyond the model requirement. Usage is only implied by the description of what it produces.

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