bungie_get_profile

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

Without annotations, the description must fully disclose behavioral traits. It only states 'Get a Destiny 2 player profile,' but fails to mention that it requires an API key (though the schema includes api_key), whether it is read-only, or what happens on errors. This is a significant gap for a tool that likely requires authentication.

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), but it lacks necessary details. Conciseness is good, but not at the expense of completeness; here it is under-informative.

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?

The tool has three parameters, no output schema, and no annotations. The description is far too minimal to be complete. It fails to provide any context about the required membershipType and membershipId, the optional api_key, or the structure of the returned profile.

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 3 parameters, all with zero description coverage. The tool description does not explain what membershipType, membershipId, or api_key represent, nor their expected formats or valid values. 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 uses a specific verb ('Get') and resource ('Destiny 2 player profile'), which clearly indicates the tool retrieves a single player's profile. It distinguishes from sibling tools like bungie_search_player (searching) and bungie_get_manifest (getting manifest 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?

The description lacks any guidance on when to use this tool versus alternatives such as bungie_search_player or bungie_get_manifest. It does not provide usage context, prerequisites, or exclusions.

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