call_adbutler_api

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

With no annotations, the description carries the full transparency burden. It discloses that the session's API key is applied automatically and forbids passing an api_key, and it demonstrates how path_params are interpolated into the path. However, it does not state what the tool returns (raw JSON, response status) or mention error/rate-limit behavior, leaving some behavioral aspects undisclosed.

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 four sentences, front-loaded with purpose and usage, followed by a compact example. No redundant text or repetition of schema details; every sentence earns its place.

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 generic raw API caller, the description covers what it does, when to use it, how to substitute path params, and the auth setup. The absence of a return format or error handling note is a minor gap, but the tool's generic nature and the existence of sibling wrappers make the description reasonably complete.

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?

The input schema already provides complete (100%) descriptions for all five parameters, so the baseline is 3. The description adds value by explaining the relationship between path and path_params with an example, and clarifying that api_key should not be passed even though it isn't a schema parameter. This pushes it above baseline.

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 opens with 'Call any AdButler API endpoint directly,' clearly stating the tool's function as a raw HTTP client for any AdButler endpoint. It distinguishes itself from the many sibling wrapper tools by adding 'Use this only when no specific tool wraps the endpoint you need,' making its scope explicit.

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 gives an explicit usage condition: only when no specific tool wraps the endpoint, which differentiates it from the extensive wrapper list. It also provides a concrete example of path placeholder substitution and warns against passing an api_key, clarifying setup expectations.

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