list_function_runs

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

With no annotations, the description carries full burden for behavioral traits. It only mentions the listing and filterability but omits whether the operation is read-only, any side effects, pagination behavior (cursor/limit details), rate limits, or authentication needs. The description provides minimal behavioral 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?

The description is a single sentence that efficiently conveys the tool's purpose and key filterable dimensions. Every word earns its place with no redundancy or fluff.

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?

Given no output schema and 8 parameters, the description provides a basic overview but does not explain return structure, default sorting, or ordering. It lacks depth about what the agent can expect after invocation, leaving some gaps for a moderately complex listing tool.

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%, so baseline is 3. The description lists some filter options (status, event_type, time window, limit, cursor) but does not add meaning beyond what the schema already provides. It serves as a high-level summary without additional detail.

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 'durable runs for a function', which is a specific resource. It distinguishes from siblings like 'get_function_run' (single run) and 'list_functions' (list functions). The mention of filterable options adds specificity.

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?

The description implies usage for listing runs but does not explicitly state when to use this tool versus alternatives like 'get_function_run' or 'cancel_function_run'. There is no guidance on prerequisites or when not to use it, so the usage context is only implied.

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