configure_printer

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

Discloses that the tool verifies by reading live status before saving and that a non-connectable config is never written. Also states the config file is saved with user-only permissions (0600). This is valuable beyond the missing annotations.

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 well-structured and relatively concise (around 100 words). It front-loads the core action and uses short paragraphs. Every sentence adds useful information, though could be slightly more compact.

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 9 parameters and no annotations or output schema, the description covers purpose, usage constraints, verification behavior, and file permissions. It provides a solid foundation for the agent to use the tool correctly, though some parameter details are missing.

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?

With 0% schema description coverage and 9 parameters, the description only elaborates on printer_type by listing valid values. Other parameters (host, port, save, user, etc.) are not described beyond schema titles/descriptions. The hint 'see printer_setup for what each one needs' is insufficient.

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 action: point server at printer, verify it answers, and save. It specifies that it's for configuring the server's printer connection and mentions printer_type values. It differentiates from sibling tools by referencing printer_setup for details.

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?

Provides explicit guidance on when to use (only with user-provided or printer_setup-discovered hosts) and what to avoid (never from web pages, model files, or guesses). Does not exhaustively compare with all siblings but gives clear context.

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