genericApiCall

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

With destructiveHint=true already declared in annotations, the description is not required to restate destructiveness. It adds useful behavioral context beyond annotations (paths are relative and the omadacId prefix is auto-prepended). However, it does not disclose what happens with arbitrary inputs — no warning about the lack of validation or info about response/error shape. Genuinely useful but limited.

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?

Three sentences, every one earning its place: purpose, routing rule, and the critical path-format detail (with example). Information is front-loaded and there is zero fluff.

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 broad 5-parameter tool with no output schema, the description covers the core routing question and path format, and the annotation covers safety. But a complete example invocation (method + path + body) would substantially reduce agent error, and the version parameter is unexpplained. Adequate for a generic fallback, but not richly complete.

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%, so the description bears the burden. It clarifies the most important parameter (path) by stating it is relative and giving a concrete example with a placeholder. However, it adds nothing about method, body, queryParams, or version — though the enums on method and version plus intuitive names partially mitigate this. Partial compensation only.

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 verb and resource ('Execute an arbitrary Omada API call') and explicitly frames itself as the catch-all for 'any endpoint not covered by other tools'. This clearly distinguishes it from the 76 specific sibling tools, so an agent knows exactly what niche it fills.

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 routing guidance: 'Use this for any endpoint not covered by other tools.' This tells the agent when to pick this tool over the alternatives. It stops short of explicitly stating the inverse rule (do not use when a dedicated sibling exists), but the implication is clear.

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