start-precheck

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. It fails to mention side effects, asynchronous behavior, required setup, or return format. It only states that a precheck is started.

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 description is a single brief sentence, which is structurally simple, but it is underspecified rather than appropriately concise. It omits critical information that should be present; this is under-description, not efficient conciseness.

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 tool is part of a precheck lifecycle (with get-precheck-status and stop-precheck siblings), but the description gives no indication of how the run is initiated, what the payload should contain, or how to track progress. With no output schema or annotations, the description is completely inadequate.

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 sole parameter 'payload' has no schema description (0% coverage) and the description does not explain its structure or purpose. The schema allows any object, so without text guidance the agent has no idea what to supply.

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 'Start a precheck run' uses a specific verb and resource, but it is nearly a tautology of the tool name. It does not clarify what a precheck is or distinguish this from the sibling tools like start-training or get-precheck-status.

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 guidance on when to use this tool, what conditions must be met, or how it relates to other precheck/training tools. The description provides no context for selection versus alternatives.

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