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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive, non-open-world operation. The description adds useful behavioral context by saying results are enriched with full text and JSON-LD schema, but it does not explain ranking, pagination, or how top_n and per_page affect returned results.

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 definition is a single front-loaded sentence with no redundant or filler content. It communicates the action, scope, and enriched return in a compact form.

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 search tool with three parameters and no output schema, the description gives only a high-level indication of return content. It does not clarify result ranking, pagination behavior, or how top_n and per_page interact, though the annotations adequately cover the safety profile.

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 baseline is 3 even though the schema's parameter descriptions are generic. The description's phrase 'top matching' loosely suggests top_n, but it adds no concrete meaning for top_n or per_page beyond the schema's 'Integer value' descriptions.

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 and resource: search site content and return top matching page contexts. It also specifies the enrichment as full text and JSON-LD schema, which distinguishes the return shape from a plain search. However, it does not explicitly differentiate itself from close siblings such as search_content or get_page_content_with_schema.

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 enrichment mention implies the tool is appropriate when full-text and JSON-LD page contexts are needed, but there is no explicit when-to-use or when-not-to-use guidance. With many search and page-content siblings available, the description leaves the agent to infer that this is the enriched variant rather than naming alternatives.

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