list_simulation_personalities

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

With no annotations, the description carries the full burden, and 'Lists' reasonably implies a non-destructive read. However, it says nothing about pagination or truncation behavior (the 50-default, 1000-max limit), whether an empty list is possible, or what fields a personality record contains — context an unannotated tool should supply.

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?

A single clause, front-loaded with the action and resource, with the colon-apposition earning its place by defining a domain term. Nothing extraneous.

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 one-optional-parameter list tool with a fully documented schema and no output schema, the description covers the essential question of what is being listed. It stops short of only minor extras such as default page size or return shape, which keeps it close to complete.

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 100% and the sole parameter 'limit' is fully documented in-schema with bounds and a default. The description adds no meaning beyond the schema, so baseline 3 is appropriate.

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 ('Lists') plus the exact resource ('simulation personalities') and then defines what that resource is — 'the simulated callers (testers) used in Vapi simulations' — a term an agent may not otherwise know. The plural verb form cleanly separates it from the create_simulation_personality sibling.

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?

Usage is only implied by the verb: an agent can infer this is the enumeration tool for personalities versus create_simulation_personality. There is no explicit statement of when to reach for this over list_simulation_scenarios or list_simulations, and no note that limit caps the result set rather than returning everything.

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