uc_request

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

No annotations provided, so description carries full burden. It warns about destructive endpoints but lacks details on side effects, reversibility, or authentication needs. For a tool capable of destructive actions, this is insufficient.

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?

Description is brief with one sentence and structured argument list. No wasted words, but could be slightly more compact.

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?

Core purpose is clear and destructive warning is helpful. However, with output schema present, description neither references nor explains return values. Missing context on error handling, rate limits, or pagination for a general API tool.

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 description must compensate. It adds some meaning (e.g., path prefix removal, method examples) but for body and query it only repeats schema info without enrichment. More detail on format or constraints would improve.

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?

Description clearly states the tool calls any Core REST API endpoint, specifying verb 'call' and resource 'Core REST API endpoint'. It distinguishes from siblings which are specific endpoint tools, making purpose unmistakable.

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?

No explicit guidance on when to use this general-purpose tool versus the many dedicated sibling tools. This omission risks misuse when a more specific tool exists.

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