discord_current_application

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'read or modify' without explaining side effects of modification, the meaning of 'installation metadata,' whether changes are reversible, or any requirements like permissions. The dryRun parameter is also not mentioned, so the tool's safety mechanisms are unknown.

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, front-loaded sentence that efficiently conveys the core purpose. It contains no fluff, but it is slightly too sparse given the tool's complexity, so it doesn't fully earn its place beyond stating the basic function.

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?

Despite having four parameters, a nested body schema, no output schema, and no annotations, the description provides almost no context. It fails to explain the tool's behavior, parameters, or return values, making it severely incomplete for an agent to invoke 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?

Schema description coverage is 0%, and the description does not explain any of the four parameters (action, body, dryRun, reason). It fails to clarify what 'get' vs 'modify' actions do, what the body object should contain, or how dryRun affects execution, leaving the agent to guess.

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 the tool reads or modifies the current Discord application profile and installation metadata, naming both the action and resource. It distinguishes itself from siblings like discord_current_bot_profile by adding 'installation metadata,' though it doesn't explicitly point to alternatives.

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 given on when to use this tool versus alternatives like discord_current_bot_profile or discord_modify_guild. There is no context about scenarios, prerequisites, or exclusions, leaving the agent without clear selection criteria.

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