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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the sentence 'its server marks it read-only, so it runs straight away' largely restates structured data rather than adding to it. The one genuinely additive detail is the description of the return shape (IDs, types, settings preview); nothing is said about result limits, pagination, or cost of large pages.

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?

Two sentences, front-loaded with the search purpose and return payload. The trailing 'Through Royally' clause is marginally redundant against the annotations but costs little.

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?

No output schema exists, and the description compensates by naming what comes back. For a read-only 7-parameter search tool the essentials are covered; only result-size/limit behavior is left unstated.

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 coverage is 100%, so every parameter (post_id, search_text, setting_key, setting_value, widget_type, element_type, site_id) is already documented, including the dependency that setting_value requires setting_key. The description adds no examples, defaults, or combination rules beyond that, so baseline 3 applies.

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 ('searches elements on a page') plus the dimensions searched (type, widget type, settings content) and the return payload. This distinguishes it from get-element-settings (single element) and get-page-structure (full tree), though it 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?

Usage is only implied: an agent can infer it is the lookup-by-criteria tool, but there is no explicit when-to-use, when-not-to-use, or pointer to the alternative tools such as emcp-tools-get-element-settings or emcp-tools-get-page-structure.

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