get_queue_trigger_logs

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, lowering the disclosure bar. The description adds that the returned records are webhook-action executions, which is useful scope context, but says nothing about volume, ordering, pagination, or the default/max limit behavior.

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 tight sentence with the core purpose front-loaded and the optional filters appended. No filler, though it is arguably terse enough to leave useful details out.

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, six parameters, and only 67% schema coverage, the description is minimally adequate. It conveys what the logs are but not the shape or volume of the response, and the required queueId/triggerId pairing is left entirely to the schema.

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 67%, with from/to/limit/issueId already documented in the schema. The description's 'optionally for one issue, time range' loosely maps to issueId and the time params but adds no syntax or semantics beyond what the schema already states. Baseline 3 fits.

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 and resource: 'Webhook-action execution logs of a trigger.' An agent can tell it retrieves logs rather than creating/updating something. It does not, however, distinguish itself from the close sibling get_queue_autoaction_logs, which is the same pattern for a different object.

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 parenthetical 'optionally for one issue, time range' hints at filtering but gives no when-to-use or when-not-to-use guidance, and never routes the agent between this and get_queue_autoaction_logs. The agent must infer the choice from the name alone.

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