callback_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention whether the operation is read-only, what callbacks are returned (active vs all), whether pagination is involved, or any side effects. The description adds no behavioral context beyond the name itself.

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 extremely short (two words), but this under-specification does not qualify as effective conciseness. It fails to provide enough information to be useful, similar to a tautological description.

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 tool with two parameters, no output schema, and many related sibling tools, the description is incomplete. It does not explain the return format, filtering behavior, or how this tool relates to callback_latest or callback_status, leaving significant gaps in understanding.

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 two parameters (limit and protocol) with 0% description coverage, and the description provides no meaning beyond the schema. The agent is left to guess what 'limit' and 'protocol' refer to, how they affect the list, or their valid values.

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 'List callbacks' uses a specific verb (list) and resource (callbacks), making the basic purpose clear. However, it does not distinguish itself from sibling tools like callback_latest, callback_status, or callback_check, which also deal with callbacks.

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?

No guidance is provided on when to use this tool versus alternatives. The description simply states the action without any context about the intended use case, differences from similar callback tools, or exclusions.

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