speechify_list_items

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that results come from a 'complete local snapshot' (useful context about data freshness), but it does not explain pagination behavior, cursor semantics, default filtering by state, or whether the snapshot is refreshed—leaving significant behavioral gaps for a 7-parameter listing 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?

The description is a single front-loaded sentence with no wasted words. It is appropriately concise, though 'normalized' is slightly jargon-heavy and could be clarified without adding much length.

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 7-parameter listing tool with no annotations and no output schema, the description is too thin. It does not explain filtering, pagination, defaults, or return characteristics, leaving an agent without enough context to invoke the tool correctly in varied scenarios.

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 7 parameters, and the description mentions none of them. It adds no meaning for kind, limit, query, state, cursor, folder_id, or recursive, so an agent gets no guidance beyond the raw schema types and enums.

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 states a specific verb ('List') and resource ('Speechify Library items') and adds scope ('from a complete local snapshot'), making the basic operation clear. However, it does not differentiate this tool from siblings such as speechify_get_item or speechify_list_jobs, so an agent must infer the distinction.

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 explicit when-to-use guidance, no mention of alternatives like speechify_get_item for single-item retrieval, and no indication of when to prefer this listing tool over other sibling tools. Usage is only implied by the verb 'List'.

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