api_get

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

No annotations are provided, so the description carries the full burden. It states this is a GET, but does not disclose authentication requirements, rate limits, error behavior, response shape, or whether arbitrary paths may expose sensitive data.

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 wasted words. It clearly communicates the core operation without 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 an unrestricted API passthrough with no annotations and no output schema, the description is missing important context about permissions, error handling, and when dedicated tools should be preferred. It is enough to understand the basic mechanism but not enough to use it safely and correctly.

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%: the path parameter is documented with an example in the schema. The description adds only that any endpoint is allowed, without format constraints or path validation rules, so baseline 3 is appropriate.

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 ('GET') and resource ('NinjaOne API endpoint'), and implicitly contrasts with the api_post sibling. However, it does not distinguish itself from the many dedicated get_* tools such as get_device or get_ticket.

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 use this generic endpoint versus the dedicated sibling tools like get_device, list_devices, or get_ticket. The agent must infer that this is a fallback for endpoints without a dedicated tool.

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