get-library-docs

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses only that documentation is fetched, with no details about return format, error behavior, pagination, or possible side effects. For a read operation with no annotation safety signals, this is a meaningful gap.

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, front-loaded sentence that states the action and the key constraint without any filler. It is appropriately sized for a simple fetch operation and contains no redundant wording.

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 simple tool with full schema coverage, the description plus schema are mostly adequate. However, with no output schema, no annotations, and an unresolved sibling relationship, the description does not explain what the returned documentation looks like or how the ID should be obtained. This is a clear but not critical gap.

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 100%, so the schema already documents all three parameters clearly, including the required library ID format and token clamping behavior. The description itself adds no parameter-level meaning beyond the ID requirement, which matches the baseline for full schema coverage.

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 uses a specific verb ('Fetches') and resource ('documentation for a library'), and notes the required input is a 'Context7-compatible library ID'. It is clear about the core operation, though it does not explicitly differentiate itself from the sibling tool resolve-library-id beyond implying that this tool consumes an already-compatible ID.

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 guidance about when to use this tool versus resolve-library-id, nor any mention of needing to resolve a library ID first. The sibling tool's existence makes this gap more significant; an agent is left to infer the relationship between the two tools.

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