bungie_search_entities

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

With no annotations, the description must carry the burden. It does not disclose any behavioral traits such as whether results are paginated, rate limits, or what constitutes an 'entity'. The description is too brief to be transparent.

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 short (6 words), which is concise but lacking necessary detail. It does not earn its place as it omits critical information that could fit in another sentence.

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, parameter descriptions, or annotations, the description is incomplete. It does not inform the agent about return format, limits, or how to effectively search. The tool requires significant prior knowledge.

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 0%, so the description must compensate. It does not explain any parameter: entityType (e.g., valid types), searchTerm (e.g., case sensitivity), or api_key (how to obtain). This leaves the agent guessing.

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 states the verb 'search' and the resource 'Destiny 2 manifest entities', clearly indicating the tool's function. It distinguishes from siblings like bungie_get_manifest (retrieves full manifest) and bungie_search_player (searches players). However, 'manifest entities' is vague without context.

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 bungie_get_manifest or bungie_search_player. There is no mention of prerequisites or typical use cases.

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