get_citations_tool

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

No annotations provided, so description carries full burden. Adds valuable directional context (forward vs backward citations) and scope ("all"). However, omits mutation safety, rate limits, pagination behavior for large citation sets, or error handling for invalid scroll_ids.

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 with zero waste. Front-loaded action ("Get"), parenthetical clarification efficiently differentiates tool semantics without verbosity.

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?

Appropriate for a single-parameter lookup tool with output schema present. Directionality clarification provides citation-network context. Minor gap: scroll_id parameter undocumented in schema requires explicit description mention for completeness.

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%, so description must compensate. References "a given scroll" which implicitly maps to scroll_id parameter, but does not explicitly document the parameter name, format, or constraints (e.g., UUID vs title). Adequate but minimal compensation for zero schema documentation.

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?

Excellent specific verb ('Get') + resource ('scrolls') + scope ('that cite a given scroll'). Crucially distinguishes directionality with parenthetical "('Cited by' — forward citations)", clearly differentiating from sibling get_references_tool (backward citations).

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?

Implies usage via "forward citations" clarification but lacks explicit when-to-use guidance. Does not name alternatives (e.g., get_references_tool for bibliography) or state prerequisites like scroll existence validation.

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