read_library_tool

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

The verb 'Read' conveys a non-destructive lookup, which is the primary behavioral signal, and no annotations are present to offload this burden. Still, the description does not disclose what happens for a missing slug, whether lookup is local or remote, or any authentication/error behavior.

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 concise sentence that front-loads the action and resource, then lists the retrieved content items without filler. Every part adds informational value.

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?

The output schema likely explains the return structure, so the description does not need to re-explain results. However, the description omits usage routing and slug semantics, so an agent might still be uncertain about how to identify the target tool or when this is preferable to list/search tools.

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?

The schema description coverage is 0% and the description never mentions the 'slug' parameter, its format, or how to obtain a valid value. The name 'slug' implies a unique identifier for the tool, but the agent receives no guidance beyond that inference.

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 leads with the verb 'Read' and clearly identifies the resource as 'a reusable tool', then enumerates the exact contents retrieved: manifest, README, path, origin, evidence, and usage instructions. This makes it easy to distinguish from sibling tools like list_library_tools, search_tool_library, and run_library_tool.

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?

The description implies when to use it: when you need a known tool's manifest, README, or usage details. However, it does not explicitly contrast with discovery-oriented siblings such as list_library_tools or search_tool_library, nor does it state any exclusions or prerequisites like knowing the slug in advance.

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