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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only a resource inventory; it says nothing about auth requirements, pagination, or what 'API balance and usage' returns, so it adds modest value 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?

Very brief and front-loaded, with the resource list first and the help hint last. It is a noun fragment rather than a full sentence ('Connected apps, API keys...'), which costs a little clarity, but nothing is padded or redundant.

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?

There is no output schema and the params object is free-form, so the help-action disclosure is the key completeness mechanism and it is present. That said, an agent still cannot tell from the description alone what the list response contains or how it relates to manage_connections.

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 coverage is 50%: the action enum is self-documenting, and the params object carries its own description. The description reinforces the discovery pattern by telling the agent to call action "help" for each action's fields, which compensates partially for the untyped additionalProperties params, but adds no field-level semantics.

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 enumerates the resources it exposes (connected apps, API keys, webhooks, API balance and usage) and the supported action (list), so an agent knows what it reads. However, it never explicitly distinguishes itself from the sibling manage_connections, leaving the read-vs-write boundary to be inferred from the get_ prefix and annotations.

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?

Usage is implied by the 'list' action and the read-scoped resource set, and the description gives a meta-hint to call action "help" for field discovery. It offers no explicit when-to-use guidance and does not route the agent to manage_connections for mutations.

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