iyke_iframe_send

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

The description discloses the fire-and-forget nature and that the bridge listens for known kinds. With no annotations, it adds some behavioral context but does not cover error conditions or prerequisites like iframe being loaded.

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 description is two sentences with no fluff, front-loaded with the verb and resource. Every word earns its place.

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 simple tool with 3 parameters and no output schema, the description covers the basic purpose and a use case. It could be improved by indicating known 'kind' values or that 'pane' must be a valid pane identifier.

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 0% with no parameter descriptions. The description only names the parameters and gives one example for 'kind', leaving 'pane' and 'payload' underspecified. It adds minimal meaning 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?

The description clearly states the tool sends a fire-and-forget postMessage to an iframe pane, with an example kind and use case. It differentiates from siblings implicitly by being the only tool for sending messages, but does not explicitly contrast with iyke_iframe_state.

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?

The description mentions using the tool to drive mini-app actions from outside the app, which gives context for when to use it. However, it does not specify when not to use it or provide alternatives like iyke_iframe_state for queries.

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