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

Annotations already declare non-read-only, non-idempotent, non-destructive and closed-world; the description adds genuine value by disclosing the return contract (signed credential only on a pass) and the auth requirement (NOVARAIL_AGENT_KEY). It omits what happens on failure, whether retries/resubmission are allowed, and why the operation is non-idempotent.

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?

Two tight clauses with the purpose front-loaded and the auth constraint appended; nothing is wasted. Brevity is achieved at the cost of omitting parameter detail, but the sentence structure itself is efficient.

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 5-parameter mutation tool with no output schema, the description covers the outcome and auth, which is meaningful. However, it leaves the undocumented optional parameters (deep, output_type) and failure-path behavior unaddressed, so an agent cannot fully predict the call's effect.

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 5 parameters, so the description carries the full burden, yet it only names two of them (task, output). The required agent_id and especially the optional 'deep' and 'output_type' flags are left entirely unexplained, and there is no indication of how agent_id relates to the auth key.

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?

States a specific verb and resource — submitting an off-platform agent's work (task and output) for verification — and names the outcome (signed credential on pass). This is distinguishable from siblings like run_checks or relay_work, though the description never explicitly contrasts them.

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?

Implies the usage context ('off-platform agent's work') and the auth prerequisite, but gives no explicit when-to-use / when-not guidance and does not name an alternative such as run_checks for in-platform verification.

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