add_printer

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

With no annotations, the description carries full burden. It discloses that plaintext tokens stay in memory only and persisted profiles use env vars. However, it omits details on update semantics, error states, or prerequisites, leaving gaps.

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 concise sentences with the key information front-loaded. Every word is necessary; no fluff.

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?

Given 15 parameters and no output schema or annotations, the description is brief. It lacks information on return value, error cases, or prerequisites (e.g., authentication). The context is sufficient for basic use but incomplete for comprehensive understanding.

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 thorough parameter descriptions. The tool description adds value beyond schemas by explaining the memory-only vs. persistent distinction, which aids in understanding parameter usage like access_token vs. access_token_env.

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 'Add or update a named printer profile', specifying the action (add/update) and resource (printer profile). It also differentiates between in-memory tokens and persisted env var references, distinguishing it from siblings like remove_printer or set_default_printer.

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 mentions token persistence behavior but does not explicitly state when to use this tool versus siblings (e.g., when to add vs. update, or when to use env vars). Usage context is implied but not clearly delineated.

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