vibemap_list_kanban_events

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

Annotations declare readOnlyHint=true and destructiveHint=false, which the description does not contradict. The description adds ordering behavior ('newest first') and the purpose of the `since` parameter, but it does not disclose other behavioral traits like pagination behavior beyond the limit parameter, rate limits, or the event structure.

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 consists of two sentences, each providing essential information without redundancy. The first sentence states the primary function and ordering, and the second sentence gives a key usage guideline. Every word earns its place, making it highly 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?

For a simple list tool with no output schema and 3 parameters, the description adequately covers the primary purpose, ordering, and a key parameter use case. It is sufficient for an agent to understand and invoke the tool correctly, though additional details about event structure or pagination would enhance completeness.

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 67% (2 of 3 parameters have descriptions). The description adds value by explaining that `since` is for reconnect-backfill, which goes beyond the schema's 'ISO timestamp; only events strictly after this are returned.' However, the `projectId` parameter lacks any description in both schema and tool description, leaving its semantics unclear.

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 kanban transition events for a project, newest first. The verb 'list' and resource 'kanban transition events' are specific, making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like vibemap_get_kanban_board, which might provide similar data in a different format.

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 provides a usage hint for the `since` parameter ('for reconnect-backfill'), which guides when to use it. However, it lacks guidance on when to prefer this tool over alternatives such as vibemap_list_changesets or vibemap_get_kanban_board, leaving the agent to infer the appropriate context.

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