vsp360_call_operation

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description nonetheless adds substantial non-obvious behavior: automatic authentication, a 100-item per-page pagination ceiling, the RFC 8288 `next` traversal model, and that binary responses (ZIP/gzip/CSV) are written to a download folder with the path returned. Error behavior and rate limits are not mentioned, keeping this short of a 5.

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?

Five tight sentences, all front-loaded with the core call contract first, then auth, then pagination, then output handling. No sentence is redundant with structured fields, and nothing is padded.

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?

For a generic dispatcher with 7 params and no output schema, the description covers the essential calling contract plus return-value handling for binary payloads. The main gap is workflow context: it does not tell the agent to resolve operationId via the sibling list/describe tools, which is the one thing an agent most needs before calling.

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 coverage is already 86%, so the baseline is 3. The description adds meaning beyond the schema by explaining that path/query/header params are passed by name in `params`, that the body is JSON for POST/PUT/PATCH, and that pagination is limit/offset capped at 100 per page with all_pages following the `next` link. This directly clarifies how the loosely-typed `params` object is populated.

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?

States a specific action and scope: call any VSP 360 REST API operation by operationId, with auth handled automatically. It is clear what the tool does, but it never differentiates itself from its siblings (list_operations, describe_operation), leaving the agent to infer that this is the execution step of a discover-then-call workflow.

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?

Usage is implied rather than stated: pagination guidance is conditional and useful ('all_pages ... GET collections only', max 100 per page), and the read-only constraint is made explicit. However, it gives no guidance on when to use this versus vsp360_list_operations / vsp360_describe_operation, nor how to obtain a valid operationId, which is the required parameter.

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