buffer_api_help

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

No annotations are provided, so the description carries the behavioral burden. It clearly indicates a read-only, introspection-like behavior by saying 'Get help', 'list all actions', and 'get detailed schema info'. It could add detail about output format or handling of unknown action names, but the core behavior is transparent enough for a help tool.

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 one clear sentence, front-loaded with the tool's purpose and then detailing the two invocation modes. Every word contributes; there is no redundancy or filler.

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 only two optional parameters, no output schema, and a simple introspection purpose, the description covers the main invocation scenarios: list everything or ask about a specific action. It could optionally clarify the return format or recommend pairing with use_buffer_api, but nothing essential to calling the tool is missing.

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 already provides 100% parameter descriptions, including that 'action' can be omitted to list all actions and that 'category' filters by query or mutation. The description reinforces the two usage modes but does not add new parameter-level meaning beyond what the schema states.

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 and resource: 'Get help on available Buffer API actions', and clearly distinguishes the two modes: listing all actions or retrieving detailed schema for a specific action. It is immediately distinguishable from the sibling execute tool use_buffer_api.

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 makes clear this is for help/schema discovery rather than executing API actions, so the intended context is inferable. However, it does not explicitly say 'use this before use_buffer_api' or state when not to use it, so exclusions and alternatives are only implied.

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