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

The description discloses behavioral traits beyond the annotations: results are 'best matches with a snippet' (so full content is not returned), language changes which site is searched, and the get_page pointer implies snippets are truncated. Annotations already cover read-only/idempotence, so these additions are meaningful context rather than repetition.

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?

Three sentences with no filler, and the core purpose is front-loaded. The enumeration of content types is long but useful for an agent deciding whether search_site covers a given topic. It earns its place, though the list could arguably 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 a 100%-described schema, an output schema, and annotations covering the safety profile, the description is complete: it covers what the tool searches, the shape of results, language behavior, and how to proceed with a full result via get_page. Nothing an agent needs to call this tool correctly is missing.

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 100%, so the input schema already documents query, type, limit, and language. The tool description adds no parameter-level meaning beyond reinforcing the language behavior and content scope. This aligns with the baseline 3 for high schema coverage.

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 starts with an explicit verb+resource, 'Search the pages on projectthunder.com', and enumerates the exact content types covered (services, platform guides, ERP integration guides, comparisons, Insights, partner directory). It also distinguishes itself from get_page by stating it returns best matches with a snippet, and from list-style siblings by emphasizing search across all these types.

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 clear alternative with 'Use get_page to read a result in full' and explains language selection behavior ('English by default; set language for the Spanish, Portuguese or Chinese site'). However, it does not explicitly state when to prefer search_site over sibling list tools like list_pages or list_articles, so it lacks explicit when-not guidance.

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