bungie_search_player

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

Description lacks any disclosure of behavioral traits: no mention of read-only nature, authentication needs, rate limits, or result structure. With no annotations, this is a critical gap.

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?

Single sentence is concise but at the expense of necessary details. It's not padded with fluff but lacks structure to convey important information.

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 search tool with no output schema, the description omits expected return data, authentication requirements, and parameter semantics, making it incomplete for informed 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?

Only membershipType has a description in the schema ('-1 for all'), but the tool description adds no semantic value. For a tool with 33% schema description coverage, the description fails to compensate.

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?

Description uses specific verb 'Search' and resource 'Destiny 2 player' by display name, clearly distinguishing from siblings like bungie_get_profile which retrieves full profile data.

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 on when to use this tool versus alternatives, no mention of mandatory api_key or appropriate membershipType values, and no context on preconditions or limitations.

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