agentbus_review

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

No annotations are provided, so the description must fully disclose behavioral traits. It indicates a read-like operation (listing), but does not explicitly state that it is read-only, whether it requires specific permissions, or if it has any side effects. More detail could be added about the non-destructive nature of the operation.

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 a single, well-structured sentence that conveys the essential purpose without any extraneous words. It is front-loaded and efficient.

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?

Given the tool has two parameters and an output schema (not shown), the description is insufficient. It does not explain how parameters affect results, potential pagination, or the structure of the output. The context is notably incomplete for effective use.

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?

The schema has 0% parameter description coverage, and the description does not explain the parameters (limit, topic) at all. The description must compensate for the lack of schema-level documentation but fails to do so, leaving the parameter semantics completely unexplained.

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 lists events pending human approval and that these are hidden from standard poll. It specifies the verb 'list' and resource 'events pending human approval', distinguishing it from siblings like agentbus_poll and agentbus_approve.

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 implies when to use this tool by noting the events are hidden from standard poll, suggesting it as an alternative to agentbus_poll for viewing pending approvals. However, it does not provide explicit when-not-to-use or mention alternatives beyond the implicit contrast with poll.

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