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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds that the returned JSON is 'internal application state for LeanrIQ and ChatGPT orchestration,' and instructs not to display raw JSON to users. It also notes synchronous execution and forbids task support, providing additional 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?

The description contains useful directives but is padded with a tautological first sentence and repetitive classification lines. The response-formatting guidance is clear but could be condensed.

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 nine undocumented parameters and an existing output schema, the description is incomplete. It lacks parameter semantics, pagination behavior, and differentiation from sibling tools, though it does provide some response-handling guidance.

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?

With 0% schema description coverage, the description must explain the nine parameters, but it mentions none of them. There is no information about limit, cursor, seatId, status, or other filters, leaving the agent to guess their semantics.

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 'list advertisers,' which merely restates the tool name and title. It does not specify what the tool returns, whether it lists all advertisers in the current seat, or any filtering semantics, thus failing to distinguish it from sibling list tools.

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?

The description provides no guidance on when to use list_advertisers versus get_advertiser or other list_* tools. It focuses on response presentation (e.g., 'Use assistantSummary first') rather than tool selection context.

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