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

Annotations already establish read-only and non-destructive behavior, but the description adds valuable return semantics: platform-specific fields, that other networks return only `platform` and `accountId`, and that an empty list means nothing is configured. It also warns that `set_bot_starters` replaces the entire list.

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 tightly written sentences front-load the core purpose, then add platform-specific return details and the key warning about `set_bot_starters`. Every sentence contributes useful information.

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 read-only, one-parameter tool with no output schema, the description gives enough context to call it correctly: what it returns per platform, how to interpret an empty list, and its relationship to the write operation. Nothing critical is missing.

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 only one parameter and schema coverage is 100%, so the schema already documents it fully. The description reinforces that it is one account and lists supported platforms, but adds no new parameter syntax or format beyond the schema.

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?

States a specific read operation and resource: the customer-facing shortcuts shown before writing to an account, broken out by platform (`menu`, `iceBreakers`, `commands`). This clearly distinguishes it from `set_bot_starters` and from unrelated sibling tools.

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?

Explicitly says to use it before `set_bot_starters`, which replaces the whole list, giving a clear usage condition relative to the main alternative. It does not state when not to use it, so it falls short of full when/when-not guidance.

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