raw_action

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the path format and that params is a positional argument list, but it does not mention return values, side effects (e.g., destructive actions), error handling, or authentication requirements, which are critical for a raw passthrough tool. The 'call any endpoint' phrasing hints at broad behavior but lacks explicit safety or response info.

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 one concise, front-loaded sentence that efficiently states purpose, gives examples, and explains the key parameter. Every phrase earns its place, with no redundant or filler content.

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?

Given no output schema and no annotations, the description provides a reasonable but incomplete picture. It covers purpose and parameter semantics but omits return values and side-effect warnings, which are especially important for an arbitrary endpoint caller. The tool's simplicity and clear role prevent a lower score, but the lack of behavioral details is a notable gap.

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 compensates by explaining that params is the positional argument list and giving an example path format. It does not explain http_action, but the name and default ('POST') make it self-evident. This adds meaning beyond the bare schema.

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 identifies the tool as a generic caller for any JD API endpoint not covered by dedicated wrappers, with concrete examples (premium accounts, captcha, reconnect, speed-limit). It distinguishes itself from sibling tools by explicitly positioning itself as the 'not wrapped above' fallback, making its 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?

It states when to use: for endpoints not wrapped by other tools, and gives examples that imply alternatives (the specialized sibling tools). While it doesn't explicitly say 'use other tools for wrapped endpoints', the phrase 'not wrapped above' plus the examples provide clear usage context.

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