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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely useful context the annotations lack — data originates from Discord's official status dashboard and each call costs 1 credit. It does not say what is actually returned (overall indicator vs. incident list vs. component uptime), and no output schema exists to fill that gap.

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 purpose and component scope are front-loaded in the first sentence, and the cost note is a useful trailing signal. The middle sentence partly restates the first ("monitor real-time connectivity... API performance") in more promotional phrasing, which is mild padding.

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?

For a zero-parameter read-only status lookup, the description covers what is checked, the source of truth, the motivating scenario, and the cost. The one real omission is the response shape — component-level statuses versus incident summaries — since no output schema exists to convey it.

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 tool takes zero parameters, which is the baseline-4 case. There is nothing for the description to disambiguate, and it correctly implies a single no-argument call.

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?

"Check the operational status of Discord's API, Gateway, and Media Proxy" names a specific verb and resource and scopes it to named Discord components. Against the many sibling status tools (slack_status, github_status, cloudflare_status), the Discord scope makes the target unambiguous without opening the schema.

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 gives a concrete usage trigger: developers seeing "stuck on connecting" or message delivery failures. However, it never names an alternative or states exclusions (e.g., use slack_status/github_status for other services), so routing guidance is contextual rather than explicit.

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