bungie_get_manifest

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

With no annotations, the description carries full burden. It says 'Get', implying a read operation, but fails to disclose important behavioral traits such as authentication requirements, response format (e.g., a URL to a JSON file), or potential rate limits. The agent cannot infer the tool's behavior beyond a basic get.

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 sentence of six words, which is concise but lacks any structure. It borders on under-specification rather than effective conciseness. A well-structured description would front-load key details and provide context.

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 annotations, no output schema, and a single undocumented parameter, the description is severely incomplete. It does not explain what the manifest definition contains, how to interpret the result, or any constraints. The agent lacks essential information to use the tool correctly.

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 schema shows one parameter 'api_key' with no description, and the tool description adds no meaning. It does not explain what the api_key is for, how to obtain it, or its role in accessing the manifest. With 0% schema description coverage, the description completely 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?

The description clearly states 'Get the Destiny 2 manifest definition' with a specific verb and resource. However, it does not differentiate from sibling tools like bungie_get_profile or bungie_search_entities, leaving room for ambiguity about what the manifest is.

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. The description does not mention prerequisites, typical use cases, or context such as whether this is a first step in interacting with Destiny 2 API.

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