mining_run

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

With no annotations provided, the description carries full burden for behavioral disclosure, yet it states nothing about side effects, mutation, read-only nature, or any operational traits. The description is entirely empty of behavioral information.

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?

While extremely short, this is under-specification rather than conciseness. The single phrase provides no structural benefit; it fails to front-load any useful information because it contains none.

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 complex tool with 10 parameters, 4 required, and no output schema, this description is completely inadequate. It provides no context about return values, side effects, or operational expectations, making it impossible for an agent to use correctly.

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?

The schema has 10 parameters with 0% coverage, and the description adds no meaning to any parameter. Required fields like repository_id and snapshot_id remain unexplained, leaving the agent to guess their formats or purposes.

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 is a tautology, repeating the tool name 'mining run' with no verb or resource specification. It provides no distinction from any sibling tool and gives an agent no reason to pick it over alternatives like mining_discover or snapshot_catalog.

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 exists on when or why to use this tool. There is no mention of prerequisites, context, or comparison to sibling tools, leaving the agent with zero direction on selection.

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