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

Discloses the two-step write protocol that annotations only hint at: non-GET methods return a preview and only execute with confirm: true, and confirm should be set only after user agreement. It also describes the return shape ('the API's own status and data'). This goes well beyond readOnlyHint=false / destructiveHint=true.

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 tight clauses: what it is, the call shape, and the GET-vs-mutation rule with confirmation. Front-loaded and free of filler.

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 complex, destructive, no-output-schema gateway tool, the description covers invocation, the confirm safety flow, and the return nature. The only minor gap is that the org parameter's scoping behavior is left entirely to the schema.

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 50% (org, path, confirm documented; method, query, body not). The description adds value by showing the request shape { method, path like "/content/items/<itemId>", query?, body? } and marking query/body optional, but leaves the body/query contents and method semantics to the reference doc.

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: 'Call any Seovyn API endpoint as the user, in one organization', and immediately points to seovyn_api_reference for the catalog the tool wraps. An agent can tell this is the generic escape hatch, distinct from the specific siblings like seovyn_brand or seovyn_get_article.

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 clear context: consult seovyn_api_reference to pick an endpoint, GET runs immediately, everything else is preview-then-confirm. It doesn't, however, say when to prefer a purpose-built sibling over a raw API call, which is the main selection decision for this tool.

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