search_entities_tool

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

Describes return structure (dictionary with count, results, domains) and gives examples. Notes that query matches IDs, names, and attributes. With no annotations provided, the description adequately covers behavior, though it could mention potential errors or performance implications.

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 well-structured with sections (Args, Returns, Examples), is front-loaded with purpose, and every sentence adds value. No unnecessary words.

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?

Given the presence of an output schema, the description adequately outlines the return format. It covers the main use case and differentiates from list_entities. However, it could mention that the tool is read-only (though no annotations exist) or provide more detail on result fields.

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?

With 0% schema coverage, the description fully explains both parameters: query as a string matching entity fields, noting wildcard limitation; limit with default 20. This adds significant meaning beyond the bare schema.

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 'Search for entities matching a query string', specifying the action and resource. It distinguishes from siblings like list_entities by noting that leaving query blank or using that tool returns all entities. Examples further clarify the purpose.

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?

Explicitly states that wildcards are not supported and suggests using list_entities for all entities. Provides default limit (20) and examples, giving clear guidance on when and how to use the tool versus alternatives.

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