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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds useful return context ('verified app page links for citations and contextual article links'), but says nothing about result caps, pagination, or behavior when query is omitted.

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 enumeration of the five apps is front-loaded and earns its space by defining scope, and the closing sentence is a clean routing rule. The density is acceptable, though the app inventory could be tightened since the enum already lists them.

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?

With no output schema, the description does at least characterize the return (verified page links plus contextual article links), which is valuable. It remains incomplete on result limits, whether an empty query returns a listing, and how it relates to the overlapping domain-specific search siblings.

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 must carry the load. It maps the app enum values to their content domains and hints that query should hold a party/faction name plus country, but the limit parameter (default 30, max 100) is never explained and there is no guidance on empty-query listing behavior.

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 specific verb (search) and resource (public content), and enumerates the five apps and the content types each covers, so an agent knows the scope. It doesn't clearly separate itself from overlapping siblings like search_politics, search_news, and search_programs, which search much of the same material.

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 a concrete usage pattern ('Search with a party or faction name and country to find its profile') and an explicit exclusion ('For lounges and cruise ships use the dedicated catalog tools'). The gap is that it never says when to prefer this tool over search_politics or search_news, which appear to cover the same domains.

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