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

With no annotations supplied, the description carries the full disclosure burden. It usefully states the traversal is bidirectional ('any direction') and discloses a cost signal ('Free · 1 credit'), but it says nothing about authorization, result limits, or what a 'connection' actually is.

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?

One front-loaded sentence plus a bracketed cost tag; nothing is wasted. The cost note could arguably be metadata rather than prose, but it is short and clearly separated.

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?

For a one-parameter read tool with no output schema, the core meaning is conveyed. Still missing are the nature of 'connected' (which relation types count) and any sense of result volume or ordering, which an agent would want before calling it.

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% for the single parameter, so the description must compensate. It clarifies that concept_id is a node id (not a name or free-text concept) and that edges are followed in both directions, but it gives no format or example for the identifier.

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 names a concrete verb-and-resource pair: papers in 'your personal library' connected to a 'Concept node id'. It also implicitly separates itself from the parallel sibling library_papers_with_method by naming the node type it traverses, though it never states that distinction outright.

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?

There is no when-to-use or when-not-to-use guidance, and no named alternative such as library_filter or library_search_nodes. The agent must infer from the phrase 'personal library' that this is scoped to the user's own saved papers rather than the global corpus.

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