Runn: list people

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

With no annotations provided, the description carries the full burden. It mentions filters and placeholders but does not disclose pagination behavior, default limits, return format, or whether the operation is read-only. The word 'List' implies read, but no explicit safety or behavioral context is given.

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, front-loaded sentences convey the core purpose and key options with zero waste. Perfectly concise for the information provided.

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?

Despite having 8 parameters and no output schema, the description omits pagination defaults, cursor usage, fetchAll behavior, and return shape. It is minimally adequate but leaves significant gaps for an agent to use the tool 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 coverage is 50%, so the description partially compensates by naming filterable fields (name/email/externalId). However, it does not explain filter semantics (e.g., exact vs partial match, AND/OR combination), and the schema already covers limit/cursor/fetchAll/includePlaceholders.

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 clearly states the tool lists people with optional placeholders and filtering by name/email/externalId. It is specific and distinct from sibling list tools, though it doesn't explicitly contrast with runn_list_placeholders.

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 is given on when to use this tool versus alternatives like runn_list_placeholders. The mention of 'optionally include placeholders' hints at overlap but doesn't explain when to prefer one over the other.

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