Raw Reddit Ads API request

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

Annotations already declare readOnly=false, destructive=true, openWorld=true, so the safety profile is covered. The description adds real context beyond that: the base URL the path is relative to and the non-obvious {"data": {...}} body-wrapping convention for POST/PATCH/PUT. It omits auth/permission requirements and rate-limit behavior, which would be valuable for a destructive open-world tool.

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?

Three tight sentences, each earning its place: what it does, when to use it, and the two non-obvious formatting conventions. The purpose and gating condition are front-loaded.

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 a raw proxy with no output schema, the description covers the essentials an agent needs: base URL, path form, and body envelope. It leaves out auth prerequisites, response/error shape, and any hint about which endpoints exist, which matters given the tool's open-world, destructive nature.

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 75% and the schema already describes path, body, and query. The description adds information the schema lacks: the base URL that 'path' is relative to and the body-wrapping convention, which materially change how an agent constructs the call. It does not clarify the query parameter value types or method semantics further.

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+resource: 'Call any Reddit Ads API v3 endpoint directly.' In a family of ~100 dedicated endpoint tools, it clearly marks itself as the raw escape hatch, so an agent can distinguish it from every sibling without opening a schema.

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?

'Use for endpoints without a dedicated tool' gives an explicit selection condition that routes the agent correctly relative to the dedicated tools. It does not, however, name specific alternatives or warn against using it when a dedicated tool exists for a mutation, so the routing is clear but not maximally explicit.

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