lookup_scroll_tool

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

No annotations provided, so description carries full behavioral burden. It provides valuable ID format context (AX-2026-00001) indicating expected input pattern. However, omits error behavior (not found cases), authentication requirements, and whether this returns full content or metadata—though output schema existence reduces the need to describe return values.

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?

Single sentence, zero waste. Action verb leads, resource follows, parenthetical example provides immediate clarification without verbosity. Every element earns its place.

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?

Adequate given single parameter and existing output schema. The ID format example is critical missing context from the schema. However, with 20+ siblings including multiple scroll operations (search, submit, review, revise, retract), explicit differentiation from those alternatives would improve invocation accuracy.

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 0% (no parameter descriptions). Description compensates by specifying the Alexandria ID format with a concrete example (AX-2026-00001), giving semantic meaning to the bare 'scroll_id' parameter in the schema. Strong compensation for schema deficiency, though explicit mapping to parameter name would strengthen further.

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?

States specific verb (look up) + resource (scroll) + scope (by Alexandria ID). The phrase 'specific scroll by its Alexandria ID' effectively distinguishes from sibling search_scrolls_tool by implying singular retrieval via unique identifier, though it could explicitly name the sibling alternative.

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 implied usage through 'specific scroll by its Alexandria ID,' suggesting use when an exact ID is known. However, lacks explicit when-to-use guidance or named alternatives (e.g., contrast with search_scrolls_tool) despite a crowded sibling space with many scroll-related operations.

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