search_content

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

With no annotations provided, the description must disclose side effects or read-only nature. It does not explicitly state that the operation is read-only, nor does it mention any potential errors, permissions, or rate limits. The word 'search' implies read-only, but it is not clearly stated.

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 description is concise and to the point in one sentence. It avoids unnecessary details and directly communicates the purpose.

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 description is somewhat vague regarding the 'discovered adapter' and does not explain the return value or output format. Given that there is no output schema, it would benefit from clarifying what the search returns, but it covers the basic operation.

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?

The description adds minimal value beyond the parameter names. 'query' and 'deviceId' are self-explanatory to a degree, but the description does not clarify that deviceId refers to a discovered media appliance or explain the type of content searched. It also does not describe the expected format of query.

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 clearly states the action ('Search content or installed apps') and the target ('a discovered media appliance'). It distinguishes from sibling tools like list_known_devices and record_watch_event, which perform different operations.

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 description does not provide any guidance on when to use this tool versus alternatives, nor does it mention preconditions or typical usage scenarios. It only states the function without context.

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