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

No annotations are provided, so the description carries the full disclosure burden, and it says almost nothing behavioral: no pagination behavior for 'limit', no note on language scoping, no indication of what a result contains or how it is used. 'Library phrases play instantly' is the only behavioral morsel, and it is vague marketing phrasing rather than actionable context.

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 with the core action front-loaded and no filler. The second sentence ('Library phrases play instantly') contributes little beyond atmosphere, so it is efficient but not maximally economical.

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 search tool with three undocumented parameters, no annotations, and no output schema, the description is too thin. An agent learns the intent but not the language parameter's behavior, the limit semantics, or anything about the returned phrases.

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% across three parameters, so the description must compensate and does not. 'By words' loosely implies free-text matching for 'query', but 'lang' and 'limit' are left completely unexplained in both the schema and the description.

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 gives a specific verb ('Find') and resource ('ready-made phrases in the Speakvora library') with the search key ('by words') stated. It is clearly a distinct operation from list_voices and speak, though it never explicitly names or contrasts those siblings.

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 statement of when to use this tool versus the alternatives, and no prerequisites or exclusions. 'Library phrases play instantly' hints at the nature of the results but does not tell the agent when to choose search_phrases over speak or list_voices.

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