api_post

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

No annotations at all, so the description carries the full burden for what is a write operation. It says nothing about authentication requirements, whether arbitrary writes can be destructive or irreversible, rate limits, or error behavior on an invalid path or body. For an unannotated raw-POST escape hatch, that is a substantial omission.

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?

A single front-loaded sentence with no filler; the verb and resource come first. It is not padded, though its brevity is a symptom of the missing guidance rather than a virtue here.

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?

With no annotations, no output schema, a nested request body, and fully arbitrary endpoint targeting, the definition leaves out too much an agent needs before calling: path formatting conventions, auth assumptions, and what a call actually returns or how failures surface.

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% and both parameters carry descriptions ('API endpoint path', 'Request body'), so the schema does the heavy lifting. The description adds no extra meaning such as path format, versioning prefix, or body shape, so the baseline 3 applies.

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: a POST request to a NinjaOne API endpoint. This clearly separates it from api_get (read) and from the purpose-built siblings like reboot_device or create_ticket. The only shortfall is that 'any endpoint' leaves the scope open, which is inherent to an escape-hatch tool.

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?

There is no guidance on when to reach for this tool instead of a dedicated sibling such as create_ticket or reboot_device, nor on when it should be avoided. 'Generic ... any endpoint' hints it is a fallback, but the agent has to infer that with no statement of prerequisites or exclusions.

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