copypass_status

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

No annotations are provided. The description does not disclose side effects, authentication requirements, rate limits, or behavior if the run_id is invalid. As a read operation, it lacks explicit statement of being non-destructive.

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?

Single sentence clearly stating the tool's purpose and scope. No redundant information; each 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?

The description lacks output format details and error handling. While it mentions 'scaffold finding count', it does not define 'scaffold'. For a simple status tool, it covers basics but could be more thorough.

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 coverage is 100% with one parameter. The description adds context by noting run_id comes from copypass_run, which is valuable beyond the schema's 'The run id returned by copypass_run' description.

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 fetches current status, notes, and scaffold finding count for a CopyPass run. It specifies the run must be started in this MCP session, distinguishing it from copypass_run which initiates runs.

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 by referencing 'started in this MCP session', but does not explicitly state when to use this tool versus alternatives like copypass_run or other status tools. No exclusions or prerequisite conditions are provided.

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