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

Beyond the readOnlyHint annotation, it discloses that the data lives on Instagram rather than Inrō, that every action hits the Graph API so the list is always current, that Instagram caps icebreakers at 4, and exactly what the list returns (question, payload, and automations with scenario_id, scenario_title, active, trigger_id, plus the trigger match mode). The 'empty automations array means tapping it starts nothing' note is a genuinely useful semantic detail that no structured field conveys.

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 text is front-loaded well but the description then spends most of its length documenting create/update/delete behavior — payload generation, trigger-breakage on reworded questions, delete params — none of which this tool can perform. That is substantial bloat that also creates confusion about the tool's actual surface.

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, the description usefully documents the shape of list results including nested automation fields, which is what an agent needs. But roughly half the content describes actions the schema rejects, so the definition is simultaneously over-explained and unclear about whether an agent should ever attempt those actions.

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 100%, so the baseline is 3, and the description adds that list takes no params. It also explains payload as 'as returned by list' and question as the text shown on the profile for the write actions — but those actions are not invocable here, so the extra meaning is only marginally useful for this tool as defined.

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 opening line is unambiguous — 'Read icebreakers — this tool changes nothing. Actions: list' — a clear verb and resource that also names the sibling handling writes. However, the rest of the description then enumerates create/update/delete with their params, which this tool's schema (action enum: ['list']) does not permit, muddying the otherwise crisp purpose.

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?

Explicit routing: reads here, and 'Anything that writes (create, update, delete) is on `icebreakers_manage` and is refused here.' That is a direct when/when-not statement naming the alternative. It stops short of saying when an agent should care about icebreakers at all (e.g., before editing a scenario that triggers on one), so it is not quite a 5.

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