call_vendor_request

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'call a request' without describing side effects, potential for arbitrary actions, error behavior, or safety concerns. This is a significant gap for an inherently opaque vendor-call 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 concise, uses a clear list format for parameters, and is front-loaded with the main action. Every sentence adds value without unnecessary verbosity.

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 description lacks critical context such as where to find vendor documentation, how request_data is structured, potential side effects, or whether the operation is safe. With no annotations and no output schema, the description is insufficient for an agent to fully understand the tool's behavior and risks.

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 0%, but the description's 'Args' section adds brief explanations for each parameter (vendor_name, request_type, request_data). While helpful, the explanations are minimal and somewhat tautological (e.g., 'The vendor's request type to call'), and do not fully compensate for the missing schema descriptions.

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 states a specific action ('Call a request registered by a third-party OBS plugin/script vendor') with a clear resource (vendor request). It does not explicitly differentiate from sibling tools, but the vendor-specific scope makes it distinguishable.

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 given on when to use this tool versus alternatives, such as standard OBS requests. The description does not mention that this is for vendor-specific extensions not covered by other endpoints, leaving usage context unstated.

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