vocametrix_generate_word_list

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

With no annotations, the description carries full burden. It states the tool generates a word list with hints and difficulty progression, which covers basic behavior, but does not disclose any side effects, permissions, or safety considerations.

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 sentences, front-loaded with the main action, zero fluff. Every sentence serves a purpose: action + use cases.

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 a nested object parameter and no output schema. Description explains purpose and use cases but lacks details on return format, number of words, or how pronunciation hints are presented, which would help the agent invoke correctly.

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 33%. The description adds no additional meaning to parameters beyond what is in the schema. For example, it doesn't explain how patientAge affects difficulty or what language codes are valid.

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 a word list targeting a specific phoneme with pronunciation hints and difficulty progression, and lists specific use cases (articulation therapy, phonological awareness drills, accent training). This distinguishes it from sibling tools that assess pronunciation or generate exercises.

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?

Description provides clear context for use (articulation therapy, phonological awareness drills, accent training) but does not explicitly state when not to use or compare to alternatives like vocametrix_generate_exercises.

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