Call any apinoa operation

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds a platform-operation catalog and fallback usage, but does not disclose response format, rate limits, auth requirements, or error behavior for direct API calls.

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 first sentence front-loads the tool's role, and the platform-operation list is structured and scannable. The list is long but serves as a necessary operation reference absent from schema enums; it could be trimmed if list_platforms already returns the same catalog.

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 open-world dispatcher with no output schema, the description covers platform/operation selection and where to find params. It still leaves return values, error handling, and operation-specific behavior unaddressed, which an agent may need before invoking.

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%, so platform, operation, and params are already documented. The description adds meaningful semantics by enumerating valid operation names per platform and pointing to list_platforms for operation-specific parameters, compensating for the lack of enums.

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 verb and resource ('Call any operation of the apinoa API directly') and frames the tool as an escape hatch for operations not covered by dedicated tools, with examples such as store catalogs, shipping quotes, and LinkedIn jobs. However, it then lists operations that overlap with siblings like search_products and get_product, so sibling differentiation is not fully unambiguous.

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?

It explicitly says to use this for what the other tools do not cover and points to list_platforms for operation parameters. It does not explicitly say to prefer dedicated tools for overlapping operations or name which siblings cover which listed operations.

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