skuuy_get_bin_requests

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

Annotations already establish readOnlyHint and idempotentHint, so safety is covered. On top of that the description discloses two traits the schema cannot: the body is truncated at 1 MB, and results may lag edge KV propagation by roughly 3-5 seconds. That timing caveat is genuinely useful for an agent deciding when to retry.

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 dense sentence plus one parenthetical, with the core purpose front-loaded and the poll-timing caveat placed where it matters. Nothing reads as filler.

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?

No output schema exists, and the description compensates by enumerating the return fields (method, headers, query params, body) and the 1 MB cap. The one gap is pagination: with limit/offset in the schema and a potentially unbounded request stream, the description should say how to retrieve captures beyond the first page.

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 only 33%: bin_id is documented in the schema, but limit and offset are bare integers with no description of pagination behavior. The description adds no meaning for these parameters either, so an agent gets no guidance on page size defaults, max limits, or how to page through captures.

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 verb (Lists) and resource (HTTP requests captured by a webhook bin), and names the skeleton that produced it (skuuy_create_webhook_bin). It also enumerates what a captured request contains, so an agent can distinguish it from skuuy_read_inbox and the other sibling read tools at a glance.

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 poll this after triggering the callback being debugged, with a concrete ~3-5 second KV propagation window, and ties it to skuuy_create_webhook_bin as the prerequisite. It doesn't name a specific alternative tool to use instead, so it falls just short of the when/when-not/alternatives bar.

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