Generic SDP API Call

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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely useful trait: write bodies are form-encoded via input_data while string bodies are sent verbatim. However it says nothing about authentication requirements, DELETE/PUT irreversibility, error surfaces, or rate limits, which are important for a tool that can mutate anything.

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?

Two tight sentences, front-loaded with the capability and immediately followed by the one non-obvious encoding rule. No filler, nothing repeated from the schema.

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 maximally generic passthrough with 4 loose params, 0% schema coverage and no output schema, the description leaves critical unknowns: reachable endpoint syntax, auth model, what comes back, and the danger profile of arbitrary DELETE/PUT calls. The single encoding note does not close the gap.

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% across 4 parameters, so the description must compensate and largely does not. It clarifies only that write bodies go in 'body' as form-encoded input_data; it never explains the endpoint format (path, version prefix, base URL), how 'params' is serialized, or the distinction between body and params.

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 clear verb+resource: 'Call any SDP v3 endpoint,' which pins down that this is a generic passthrough rather than a resource-specific operation like the many sibling tools. What's missing is any gloss on what 'SDP' is or what class of endpoints are reachable, so the agent must infer scope.

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?

There is no when-to-use guidance at all, and this is precisely the tool where it matters most: the agent needs to know this is the fallback for endpoints with no dedicated tool (e.g. use get_request rather than sdp_call GET /requests/{id}). No exclusions or alternatives are named.

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