admin_list_vendors

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

With no annotations and only a two-word description, no behavioral traits are disclosed. The agent cannot infer whether the tool is read-only, what data it returns, or any constraints like pagination. The description carries the full burden and fails to provide any transparency.

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 but fails to earn its place as it adds no value beyond the tool name. It is under-specified rather than efficiently informative.

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 simplicity of the tool (no parameters, no output schema), the description should at least indicate the nature of the returned data (e.g., 'Returns a list of all vendors'). It is incomplete and leaves the agent with no understanding of the tool's output or behavior.

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 tool has zero parameters and schema coverage is 100% (vacuously). Baseline for 0 parameters is 4. The description adds no parameter info, but none is needed. Thus, a score of 4 is appropriate.

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 vendors' restates the tool name 'admin_list_vendors' without adding any additional context or distinguishing features. It is a tautology, as it merely repeats the action implied by the name.

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 guidance is provided on when to use this tool versus alternatives. There are many list tools (e.g., admin_list_users, admin_list_purchase_orders), but the description offers no criteria for selection.

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