search_actors

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the search matches on name or nickname fields, which is useful, but it does not state whether the search is partial or exact, case-sensitive, or what the return format is, nor does it explicitly confirm a read-only operation.

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 extremely concise: a single sentence of six words that front-loads the verb and resource. No wasted words, and it efficiently conveys the key distinguishing detail without unnecessary elaboration.

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?

For a simple one-parameter search tool with no output schema or annotations, the description is minimally adequate but leaves gaps. It tells what is searched (actors by name/nickname) but does not specify the result type, behavior (e.g., partial vs. exact match), or any limits, which are important for an agent to fully trust the invocation.

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 schema covers the single parameter searchTerm with a generic description, but the tool description adds specific meaning by indicating that the term is matched against 'name or nickname.' This enriches the schema description and clarifies the parameter's semantic role beyond the generic 'search term to find actors.'

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 uses a specific verb 'Search' with a clear resource 'actors' and adds the modifier 'by name or nickname', which tells exactly what the tool does. It clearly distinguishes from sibling tools like create_actor or update_actor by focusing on searching.

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 implies usage when looking up actors by their name or nickname, but it does not provide explicit guidance on when to use this tool versus alternatives such as search_enemies or search_items. It also does not mention any exclusions or prerequisites.

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