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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only a definition of what ice breakers are, not behavior: it does not say whether it returns currently configured prompts, an empty list when none are set, or how many items come back.

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?

It is a single short sentence with no waste, but it is a fragment rather than a front-loaded statement of action and resource, so brevity comes at the cost of specification rather than from efficiency.

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?

With no output schema, two undocumented required parameters, and no statement of what the call returns, the description leaves the agent without enough information to invoke the tool confidently or interpret the result. For a simple read tool it needs at minimum a verb, the return shape, and the account/connection requirement.

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 only 33% — connection_id and account_id are required but entirely undocumented, and only brand_id carries a description (which references list_brands). The tool description supplies no parameter meaning at all, so it does not compensate for the coverage gap on the two mandatory parameters.

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 identifies the resource — the ice-breaker prompts Instagram shows when someone opens a new chat with the account — but it is a bare noun phrase with no verb, so it never states that the tool retrieves/returns the configured list. A sibling named set_ice_breakers exists and is not mentioned, leaving the read-vs-write distinction to inference from the name alone.

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 guidance on when to call this versus set_ice_breakers, nor any precondition such as needing an existing Instagram connection or account. The agent must infer usage purely from the tool name and the sibling list.

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