get_citation_graph

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

Annotations already signal read-only, idempotent, open-world behavior. The description adds useful context beyond annotations: it queries OpenAlex and flags each result with in_library. It does not cover rate limits or pagination, but the safety profile is already carried by 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?

Three compact sentences with no waste: the first states the core operation and source, the second gives usage triggers, and the third notes the result flag and direction choices. Well front-loaded.

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 an output schema and read-only annotations present, the description sufficiently orients the agent with purpose, usage, output flag, and direction values. The only minor gap is not addressing how this relates to similar sibling tools like find_related_papers.

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 the description must compensate. It explains the direction enum values and indicates item_key identifies a Zotero item, but it does not clarify limit semantics or item_key formatting. Partial compensation only.

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 a specific verb and resource: 'Get papers that cite or are cited by a Zotero item' via OpenAlex. It clearly conveys the citation-network scope and direction options, though it does not explicitly distinguish itself from the sibling find_related_papers.

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 usage context: 'Use this when the user wants to explore a paper's citation network, find related work, or trace the influence of a paper.' It does not mention when not to use it or name alternative tools, but the usage context is clear.

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