bungie_get_manifest

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds nothing beyond that: it does not mention that a manifest dump is likely very large, whether results are versioned/cached, or what form the 'definition' takes. With a 6-word description there is essentially no behavioral context beyond the annotations.

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?

A single front-loaded sentence with no wasted words. It is efficient, though the brevity borders on under-specification rather than tightness.

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?

With no output schema and no annotations covering returns, the description should indicate that this yields a large manifest dataset (and roughly what it contains). It leaves the agent with no idea of payload size or structure, which matters for a manifest-fetch tool.

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 single parameter api_key has 0% schema description coverage and the description says nothing about it, leaving an agent to guess whether a Bungie API key is required, optional, or where to obtain one. Since one parameter exists and is undocumented everywhere, the baseline-4 zero-parameter rule does not apply.

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?

States a specific verb (Get) and a specific resource (the Destiny 2 manifest definition), which is distinct from sibling bungie tools like search_player and get_profile. However, it never explicitly says how it differs from bungie_search_entities, which also touches manifest data, so sibling differentiation is implied rather than 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?

There is no guidance on when to call this versus bungie_search_entities or bungie_get_profile, no mention of prerequisites, and no exclusions. An agent must infer usage entirely from the name.

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