search_actors

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Search actors by name' and does not disclose return format, pagination, case sensitivity, or whether it returns a list or single match. This is a significant gap for a search tool without annotations.

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 a single four-word sentence that is front-loaded, concise, and free of redundancy. It states exactly what the tool does without waste.

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 no output schema, the description should explain what the tool returns, but it does not. It also lacks usage context and does not distinguish itself from similar sibling tools. The description is too minimal to be fully complete for an agent to invoke correctly without additional assumptions.

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 100%: the parameter searchTerm has a description 'The search term to find actors'. The tool description adds no additional meaning beyond repeating the schema, so the baseline of 3 applies. No format, matching behavior, or constraints are described.

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 'Search actors by name' uses a specific verb and resource, clearly indicating the tool's purpose. It implicitly distinguishes from siblings like search_items or search_skills by mentioning actors, but it does not explicitly differentiate from get_actors or search_actors alternatives, so it falls short of a 5.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that get_actors might be used for listing all actors, nor does it clarify whether search supports partial matching. There is no explicit usage context or exclusion criteria.

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