pilot_set_header

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

No annotations provided; description burdens transparency. It discloses auto-redaction of sensitive values and claims no errors, but lacks info on overwrite behavior or persistence across navigation.

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?

Description is well-structured with clear sections (use when, parameters, return, errors). Slightly verbose but front-loaded with purpose.

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 2-param tool with no output schema or annotations, the description covers purpose, usage, parameter examples, return format, and error handling. Adequately complete.

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 basic descriptions. The description adds concrete examples ('Authorization', 'Bearer token123'), adding meaning beyond the schema.

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 sets a custom HTTP request header for subsequent requests, with examples (Authorization, API key, Accept-Language). It distinguishes from sibling tools like pilot_set_cookie and pilot_auth.

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 explicitly says when to use ('when the user wants to add an authorization header...'), but does not mention when not to use or alternatives. Still, it provides clear context.

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