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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the filtering behavior but says nothing about result ordering, whether filters are AND-combined, pagination limits, or what happens when a filter matches nothing.

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?

One front-loaded sentence with the resource first and the filter vocabulary after. No filler, no restatement of the title, and every clause maps to a real parameter.

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 an eight-parameter read tool with no output schema and zero schema descriptions, the description covers the filter surface adequately. The remaining gap is pagination behavior (page/per_page defaults exist in the schema but the description never signals that results are paged), which an agent would want to know for large result sets.

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 carries the load and does so for six of eight parameters: customer_id, customer_uuid, title_query (clarified as substring matching), advertisement_tag, advertisement_type and advertisement_group. It omits page and per_page entirely and does not clarify the relationship between customer_id and customer_uuid beyond "or".

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 and resource ("List advertisements") and enumerates the dimensions it can be filtered by. An agent can distinguish it from get_advertisement (single item), create_advertisement, and edit_advertisement, though the description never names those siblings explicitly.

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 word "optionally" implies filters can be combined or omitted, which is mild usage guidance. However, there is no explicit when-to-use guidance, no mention of when to prefer get_advertisement for a single record, and no note on paginating large result sets.

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