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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one piece of real operational context beyond that: the result cap of 25. It says nothing about result shape or ordering, though an output schema exists to cover the return format.

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 compact clause with the action, target, and constraint front-loaded and no filler. It is terse to the point of omitting guidance the agent would need, but nothing in the sentence is wasted.

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?

The output schema relieves the description of explaining return values, and the annotations carry the safety profile. What is missing is sibling differentiation and any hint about the connection_context parameter, which matters for a tool in a crowded targeting/interests family.

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 compensate. It clarifies that 'query' is a keyword search and bounds 'limit' at 25, but it never explains the required 'connection_context' token format, leaving one of three parameters undocumented.

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 ('Search') and resource ('Meta interest IDs') plus the lookup mechanism ('by keyword'), so an agent can tell it apart from interests_list or interests_get. It does not, however, contrast itself with the closely related sibling targeting_search.

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?

No when-to-use or when-not-to-use guidance is provided, and no alternative is named despite several overlapping siblings (targeting_search, interests_list, interests_get). The only usage-style information is the limit cap of 25.

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