jobdash_add_metrics

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

No annotations exist, so the description carries the full burden of behavioral disclosure, and a single clause reveals nothing about side effects, files modified, configuration changes, or required permissions. "Add" implies a mutation but gives no hint of scope or reversibility, which is a significant gap for a write-style tool.

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 four-word sentence is lean and contains no filler, so structurally it is clean. Yet the brevity reads as under-specification rather than deliberate pruning, since it omits usage and behavior information a tool of this kind needs.

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 mutating tool with no annotations, no output schema, and a required directory parameter plus an unexplained optional api_key, the description is far too thin. An agent cannot determine what will happen to the project directory, what the metrics look like, or what the expected result of the call is.

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 only 50%, and the description adds no parameter meaning beyond the schema. The api_key parameter is entirely undocumented, and the description does not explain how directory relates to adding metrics or what the function of api_key is.

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?

"Add" is a specific verb and "job performance metrics" identifies the resource, which distinguishes it from nearby siblings like jobdash_add_alerts (alerts) and jobdash_generate_ui (UI generation). However, it never states what form the metrics take or where they are written, so it stops short of full clarity.

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 for when to use this tool versus alternatives such as jobdash_add_alerts or exp_add_metrics. There is no mention of a prerequisite, a target project type, or any condition that would select this tool over its siblings.

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