form_draft_letter

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

No annotations and minimal description. Discloses only the action (generate) but not behavioral traits like whether the letter is saved, editable, or requires specific permissions. With no schema descriptions, the agent has little insight.

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?

Single sentence is concise but omits essential detail for a 3-parameter tool. Under-specification reduces usability, though the structure is front-loaded.

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?

Tool has 3 parameters with no schema descriptions, no annotations, and a terse description. Despite having an output schema, the overall definition is incomplete for reliable agent invocation.

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 description coverage is 0%, and the description adds no meaning to parameters like letter_type (expected values?), applicant_name, or details. Agent must guess parameter usage from names alone.

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 generates draft formal letters for Kenya civic requests, a specific verb+resource. It distinguishes from sibling tools like guides and checklists, but the 'DEMO' tag introduces ambiguity about its readiness.

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 on when to use this tool vs alternatives like form_checklist or ecitizen_guide. No exclusions or prerequisites mentioned.

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