get_report_queries_ad_gpos_details

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

With no annotations, the description carries the behavioral burden. It does disclose that this is a read-only GET operation, but it omits any mention of authentication requirements, rate limits, or other side-effect/behavioral context.

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?

Two short sentences with no filler. The action and endpoint are front-loaded, and the parameter-location guidance is compact and easy to parse.

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 0% schema coverage and no annotations, the description is under-specified: it does not say which route IDs are expected, what filters/pagination parameters exist, or whether authentication is needed. The presence of an output schema helps, but request semantics remain too vague for reliable invocation.

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 0% and all parameters are generic objects. The description adds some meaning by mapping path_params to route IDs, query to filters/pagination, and headers to required request headers, but it gives no specific key names or formats and ignores the body parameter.

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 states a clear action ('Retrieve ad gpos details') and names the exact endpoint. It is specific about the resource, though it does not explicitly differentiate itself from the similar sibling get_report_queries_ad_gpos_view.

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?

No guidance is given on when this tool should be used instead of alternatives, nor are any exclusions or prerequisites mentioned. The description only explains mechanics (where to put parameters), not selection context.

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