external.library_list

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. The description does not state whether this operation is read-only, destructive, or requires special permissions. There is no mention of side effects, performance implications, or what happens if the session is invalid. For a tool with zero annotations, this is a critical 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 extremely concise at just two words, but it under-specifies the tool's function. Conciseness requires that every sentence earns its place; here, the single sentence is too minimal to be useful. A decent description can be short, but this lacks essential details, making it an under-specification rather than efficient communication.

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?

Given the context of a complex environment with many sibling tools, no output schema, and only one minimally documented parameter, the description is severely incomplete. It does not explain the return format, whether results are paginated, or how errors are handled. For a tool that likely returns a list, the agent has no idea what to expect.

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 input schema has only one parameter (session_id) with zero schema description coverage (0%). The description does not explain what session_id means, its format, or how to obtain it. Since the description fails to add any meaning beyond the bare property name, and the schema provides no documentation, this is inadequate. The baseline is low, and the description does not compensate.

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 'List external libraries' clearly states the action (list) and the resource (external libraries). However, it does not define what an 'external library' is in this context, and among the many sibling tools like external.library_add, external.library_remove, and type_library.list, it lacks differentiation. The purpose is minimally clear but not specific enough to distinguish it from similar concepts.

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?

No usage guidelines are provided. The description does not mention when to use this tool versus alternatives like type_library.list or external.library_add. There is no context about prerequisites (e.g., having a valid session) or when not to use it. The agent receives zero guidance on tool selection.

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