bungie_search_player

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

No annotations are provided, and the description offers no behavioral information. It does not disclose whether the search is read-only, requires API key authentication, has rate limits, or returns partial matches. The description is silent on all behavioral aspects.

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 (one sentence, 7 words). While it avoids fluff, it is too minimal to be informative. It earns a pass for brevity but lacks necessary detail, making it adequate but not optimal.

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 complexity (three parameters, no output schema, many sibling tools), the description is highly incomplete. It does not explain the return format, pagination, error handling, or how membershipType filters. The agent receives insufficient context to use the tool effectively.

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 input schema has three parameters with only 33% coverage (membershipType has a description '-1 for all'). The description adds no parameter details. The required displayName has no description, and api_key lacks context. The description does not explain how membershipType values affect results or what 'all' means.

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 a Destiny 2 player by display name. It specifies the verb 'search' and the resource 'player', and distinguishes from sibling tools like bungie_get_profile (which gets profile by ID) and bungie_search_entities (which searches generic entities). However, it does not elaborate on the search scope or what information is returned, slightly reducing clarity.

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 like bungie_get_profile or bungie_search_entities. It does not mention prerequisites, preferred contexts, or exclusion criteria, leaving the agent to infer usage without support.

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