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

With no annotations, the description carries the full burden and does add two behavioral facts: pagination is bounded and certain features are absent. This is useful context for a search tool, but it omits safety, return shape, ordering, and any side effects, so the disclosure is only partial.

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 extremely compact: two short clauses with no filler. The alias statement is front-loaded and the constraints follow cleanly. It is economical and well-ordered, though the brevity sacrifices substantive guidance, which is assessed under completeness.

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 tool with seven parameters, no schema descriptions, no annotations, and no output schema, this description is severely incomplete. It does not explain how filters interact, what results look like, or how pagination parameters should be set. An agent cannot reliably call this tool correctly with only this definition.

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 description coverage is 0%, so the description is the only place that could explain the seven parameters. It does not mention query, suite, domain, offset, card_id, product, or limit beyond their raw schema types, and thus provides no semantic meaning whatsoever for any 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 identifies the tool as 'ChatGPT alias of search_evidence' but never states what it actually does, such as what it searches or across what resource. It relies on the sibling tool's identity rather than defining a clear verb+resource, making the purpose only implicit and close to a restatement of the name.

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 names search_evidence as the base tool and explicitly lists limitations ('Bounded pagination; no oracles or who_is_best'), which implies when the richer search_evidence might be needed. However, there is no direct 'use this when...' or 'use search_evidence when...' instruction, leaving selection partly to inference.

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