eight_search_person

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

No annotations are present, so the description must carry the full burden. It mentions the default source scope and the effect of source='all', but lacks details on pagination behavior (perPage, networkLimit), potential rate limits, or safety implications. The behavior is only partially disclosed.

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 very concise (two clauses), front-loading the key purpose. It efficiently conveys the default behavior and the optional source parameter. However, it could be slightly more verbose without losing conciseness to cover more parameters.

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 (so return values don't need explanation), the description provides a basic understanding of the search scope. However, for a tool with 4 parameters, the missing explanations for query, perPage, and networkLimit leave gaps. It is adequate but incomplete.

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 should explain all parameters. Only the 'source' parameter gets partial explanation (default vs all). The 'query' parameter is not described, and 'perPage' and 'networkLimit' are completely undocumented. The description adds minimal value beyond the 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 the tool searches for person cards, with a default scope of registered cards and optional expansion to public network. The verb 'search' and resource 'person cards' are specific, and the sibling 'eight_fetch_person' suggests a distinction between searching and fetching, though not explicitly stated.

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 guidance is provided on when to use this tool versus alternatives like eight_fetch_person. The description does not mention prerequisites, use cases, or when not to use it, leaving the agent to infer.

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