switch_novel

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

No annotations provided, so the description bears the full burden. It discloses that the tool sets a default novel for subsequent operations. This covers the main behavioral trait, though it omits details like session scope or error handling. Adequate for a simple switch operation.

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 a single sentence with parenthetical clarification. It is front-loaded with the action, efficient, and contains no wasted words. Perfect conciseness.

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?

Despite its simplicity, the description covers all essential aspects: purpose, parameter source, and effect on future operations. With no output schema and a single parameter, the description is fully complete for the tool's complexity.

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 description for book_id. The tool description adds value by suggesting to use list_novels to obtain the ID, which goes beyond the schema. This extra guidance merits a 4.

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: 'switch the current novel to operate on'. It specifies the parameter (book_id) and the effect (subsequent operations default to this novel). This distinguishes it from siblings like list_novels or get_current_novel.

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 advises to use list_novels to find the book_id and explains that the selection persists until switched again. It implies usage before publishing/querying, but does not explicitly list when not to use or alternatives. Slightly incomplete for a perfect score.

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