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 elsewhere. The description contributes nothing further — no indication of what is returned, whether auth/connection is required, or how it behaves on an invalid instance_id.

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?

Three words with zero waste, but the brevity comes from under-specification rather than disciplined editing. Nothing is front-loaded beyond the verb because there is nothing behind it.

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 1-parameter read tool with no output schema, the description should at minimum say what settings object comes back or how it relates to set_settings. Instead it leaves the return shape and its distinction from whatsapp_get_wa_settings entirely unstated.

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?

There is a single required parameter, instance_id, and schema description coverage is 100% ('WhatsApp instance ID'), so the schema carries the semantics. The description adds no extra meaning, but the baseline of 3 applies when the schema does the work.

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 restates the tool name/title almost verbatim: 'Get instance settings' adds only the word 'instance' over the title 'Get Instance Settings'. It does not say which settings (proxy, webhook, behavior toggles) are retrieved, and it fails to distinguish itself from the sibling whatsapp_get_wa_settings, which plausibly overlaps.

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 when-to-use guidance, no prerequisite (e.g., instance must be connected), and no mention of the alternative whatsapp_get_wa_settings or whatsapp_get_instances. The agent must guess between two similarly named settings getters.

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