Read From Component Trigger

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe external read, and the description adds that it targets a trigger on a running flow and returns that component's response. It does not disclose whether invoking a webhook trigger causes the flow to execute, whether authentication is required, or how errors are surfaced, which are important behavioral details for a live-flow trigger.

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?

A single front-loaded sentence with no filler. The action, target resource, and distinguishing constraint are all packed into one compact statement.

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 three parameters, one nested query object, and no output schema, the definition covers the call adequately but leaves the return value vague: it only says the component's response is returned, without indicating its format or how failures appear.

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 100%, so flow_id, component_id, and the nested query object are already documented in the schema. The description adds nothing beyond that, such as how query keys map to webhook parameters, so the baseline 3 applies.

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 names a specific action and resource: it sends a GET request to a trigger component and returns that component's response. It also scopes the use case to webhook triggers that listen on GET, which meaningfully distinguishes it from the sibling trigger_component tool without naming it explicitly.

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 condition for use is clear: webhook triggers that listen on GET. It never explicitly says when not to use it or directs the agent to trigger_component for POST-style triggering, so the alternative is only implied by the GET restriction rather than stated outright.

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