pilot_help

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

No annotations are provided, so the description carries the full burden. It discloses what the output will contain ("The reply describes the supported commands and filter parameters") and implies a read-only nature via "Fetch." However, it does not explicitly state side effects or permissions, though for a help tool these are minimal. Still, it adds some context beyond the name.

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 two sentences, front-loaded with the core action, and every word earns its place. It is concise without sacrificing clarity.

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 simple tool with one parameter and no output schema, the description fully covers purpose, usage context, and expected return content. It is sufficiently complete given the tool's low complexity and sibling context.

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 input schema has 100% coverage, with the single parameter 'agent' described as "Specialist hostname... or peer hostname." The description adds no additional meaning beyond restating that it's for a specialist or peer, so it meets the baseline without enhancing parameter understanding.

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's function: "Fetch the /help schema for a specialist or peer." It uses a specific verb (fetch) and resource (help schema), and distinguishes itself from siblings by explicitly relating to pilot_query ("before calling pilot_query").

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 gives explicit when-to-use guidance: "Use this to learn what /data filters the specialist accepts before calling pilot_query." It doesn't explicitly mention when not to use or name alternative tools, so it stops short of a 5, but provides clear contextual usage.

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