Call a Xyte API endpoint

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

The description adds behavioral context beyond annotations: it explains that mutating endpoints run unless the server is read-only, and that DELETE operations require a confirm parameter. This matches the destructiveHint annotation and provides important safety details.

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 description is two sentences with zero waste. The most critical information (invocation, prerequisite, mutability, confirm requirement) is front-loaded and clearly conveyed.

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?

The description is concise and appropriately relies on sibling tools for parameter details. With an output schema present, return values don't need elaboration. The description covers the essential behavioral and usage aspects for a generic API caller.

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 baseline is 3. The description adds value by noting that path parameters are all required and query parameters only accept names listed by xyte_endpoint_describe, which is not evident from the schema alone.

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 clearly states it invokes a Xyte API endpoint by key, which is a specific verb+resource. The sibling tools (xyte_endpoints_list and xyte_endpoint_describe) serve different purposes, so this tool is well-distinguished.

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?

The description explicitly advises to use xyte_endpoint_describe first if unsure of parameters. It also clarifies that mutating endpoints run unless the server is read-only, and DELETE requires a confirm parameter. This provides clear when-to-use and prerequisite guidance.

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