start_print

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

No annotations provided, so description carries full burden. It discloses the approval requirement and behavior for unsupported clients, which is important for a potentially destructive action. It doesn't detail post-start effects or session status changes, but the key behavioral traits are covered.

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 most critical information (approval requirement). Every sentence adds value without unnecessary detail.

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?

With no output schema, the description could elaborate on return values or post-print state, but it sufficiently covers the approval flow and failure scenario for a simple action. It lacks detail on success response, but the context is adequate.

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%, so description should explain the single parameter (session_id). However, it does not explicitly describe session_id; it only implies its role from tool context. This is insufficient for full clarity.

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 'Start printing a configured, sliced session — ASKS YOU TO APPROVE FIRST.' It specifies the action (start printing), the resource (configured, sliced session), and the key approval behavior. This distinguishes it from sibling tools like create_print_session or get_print_session.

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 explains that the tool prompts for explicit confirmation and only proceeds on affirmative response, with a fallback for unsupported clients. This provides clear context for when to use it, though it doesn't explicitly state when not to use it or list alternatives.

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