list_wandb_runs

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'List all runs' but does not mention pagination, return format, whether it includes archived runs, or any authentication requirements. For a listing tool, such omissions leave the agent uncertain about response size and handling.

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, efficient sentence with a clear verb, resource, and scope. It is front-loaded and contains no filler, achieving high conciseness and readability.

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 the tool's moderate complexity and the presence of an output schema (though not shown), the description still lacks critical context: no pagination info, no differentiation from siblings, and no mention of what 'all runs' implies (e.g., filtering, ordering). It feels underspecified for an agent that must decide when to use it and what to expect.

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%, but the description adds no meaning beyond the parameter names. It references 'given W&B project' but does not clarify that 'entity' is the W&B entity/namespace and 'project_name' is the project identifier, nor does it provide examples or constraints. The agent is left to infer parameter roles from the schema alone.

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 explicitly states 'List all runs for a given W&B project' – a clear verb (list), resource (runs), and scope (W&B project). This clearly distinguishes it from siblings like get_run_details (single run) and get_wandb_projects (list projects), so an agent can confidently select it for bulk listing.

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. It does not mention, for example, that for a single run's details one should use get_run_details, or that to explore available projects one should use get_wandb_projects. The description leaves selection entirely to the agent's inference.

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