ps_score_items

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

No annotations are provided, so the description carries the full burden and carries almost none of it. 'Into the scored stage' hints at a state transition/mutation of a run, but there is no disclosure of permissions, reversibility, side effects, or idempotency.

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?

It is short and front-loaded, but the brevity is under-specification rather than conciseness. Every word is a restatement of the tool name and contributes no actionable information.

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?

Even though an output schema exists (removing the need to document return values), the definition provides no annotations, no parameter semantics, and no usage context for a four-parameter pipeline tool. An agent cannot reliably decide when or how to invoke it from this description.

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% across four parameters (run_id, config_path, source_stage, periscope_path), and the description says nothing about any of them. The defaults 'raw' and null behavior are equally unexplained, so nothing compensates for the coverage gap.

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 restates the tool name with a circular phrase: 'Score a stage into the scored stage.' It never says what scoring means, what gets scored, or what items (ps_score_items) have to do with stages. It names a verb and a noun but no meaningful resource semantics.

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?

There is no when-to-use guidance and no reference to any alternative. The mention of 'stage' faintly implies membership in a pipeline workflow that includes siblings like ps_run_pipeline or ps_get_run_stage, but nothing tells the agent when to pick this tool over them.

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