list_project_metrics

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

No annotations are provided, so the description carries the full burden. It discloses a key behavioral trait: the result is a set of unique metric names rather than raw metric entries, and the scope is limited to metrics logged in the project. It does not mention pagination or ordering, but for a simple list operation this is adequate.

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?

One sentence with no filler, action and object front-loaded. Every word earns its place.

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 simple two-parameter list operation with an output schema, the description is mostly complete, but it leaves entity semantics and usage context implicit. An agent familiar with W&B conventions could call it correctly; one without that background may struggle.

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%, so the description must compensate. It only hints at project context through 'in a W&B project', which maps to project_name, but it does not explain that entity refers to the W&B entity/team or define the expected format. An agent lacking W&B domain knowledge would have to guess.

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 uses a specific verb ('List') and a specific resource ('all unique metric names logged in a W&B project'). This clearly distinguishes it from sibling tools like get_run_details, get_wandb_projects, list_wandb_runs, and plot_run_metric, which target runs, projects, or plotting rather than metric name enumeration.

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 intended use is implied by the resource description, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives. An agent can infer the tool is for retrieving metric names, but is not told when this is preferable to listing runs or plotting a metric.

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