generic_call

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the schema_lookup prerequisite and method-to-param mapping, but says nothing about destructive semantics (DELETE endpoints), auth/refresh_host usage, rate limits, error shapes, or whether POST save is upsert vs insert. For a tool that can mutate any resource, these omissions are notable.

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?

Four sentences, each carrying distinct required information (dependency, GET pattern, POST pattern, DELETE pattern). Front-loads the critical schema_lookup prerequisite. No waste.

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?

No output schema and no annotations, so the description is the sole source of behavioral context. It covers the calling convention well but leaves mutation semantics, auth/refresh flow, and response handling unaddressed for a tool capable of arbitrary resource mutation.

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 100% and the schema already documents body as 'JSON body for POST' and params as 'Query params for GET/DELETE'. The description reinforces the mapping and adds the DELETE id/number example, but largely restates schema content. Baseline 3 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?

States a concrete verb+resource ('Call any Accurate Online endpoint') with an explicit dependency, and it is distinguishable from siblings by being the invocation mechanism while schema_lookup is the discovery mechanism. Lacks specificity about which endpoint families exist, but the generic nature is intentional.

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?

Gives explicit prerequisites ('Always run schema_lookup on the endpoint first') and routes by HTTP method to the correct parameter bucket (GET/DELETE -> params, POST -> body) with concrete examples including id vs number for DELETE. This is exactly the when/when-not guidance needed for a generic dispatcher.

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