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

Annotations already disclose that this is a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's silence on safety is acceptable. Beyond that it adds nothing: no indication of result volume, pagination, or what the returned IDs look like, which is the kind of context that distinguishes a search tool from its siblings.

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?

A single front-loaded sentence with no filler, so it is efficiently sized. The terseness borders on under-specification rather than waste, which is a completeness problem rather than a conciseness one.

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?

An output schema exists, so return values need not be explained, but for a 4-parameter tool with 0% schema coverage the description leaves too much unknown: what the enum types mean, whether connection_context is required for certain account contexts, and how results are bounded. An agent could invoke it but not confidently.

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 full burden and only partly meets it: 'by type and keyword' loosely maps to targeting_type and query, but the 10 enum values, the meaning of limit, and especially the connection_context pattern token (mctx_v1_...) are left completely unexplained.

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), resource (Meta targeting IDs) and the filter axes (type and keyword), so an agent understands the operation immediately. It does not, however, differentiate itself from a conceptually overlapping sibling such as interests_search, which an agent might reasonably choose instead.

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?

There is no statement of when to use this tool versus interests_search or interests_list, and no prerequisite or exclusion guidance. The only usage signal is the implied 'you have a keyword and a targeting type', which is inference, not guidance.

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