wealthbox.events.list

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to mention return data format, pagination behavior, default limits, or how the filters interact. Listing parameter names without explaining their meaning adds no behavioral insight.

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 short but the query parameter list is redundant with the schema and not front-loaded with the most important usage guidance. It is under-specified rather than concisely informative, as the list does not earn its place by adding clarity.

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?

This tool has no annotations, no output schema, and a nested query object with ten parameters. The description is severely inadequate: it fails to explain filter semantics, pagination, or return values, leaving an agent without critical information to invoke the tool correctly.

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 already provides the parameter names, but with 0% description coverage, the description must explain what each parameter does (e.g., date formats, filtering logic). It merely repeats the names from the schema, providing no semantic value beyond what is already structured.

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 'List events' as a verb+resource, indicating a collection-returning operation. It also enumerates query parameters, which implies filtering capability and distinguishes it from a single-resource 'get' operation. However, it does not explicitly differentiate from sibling tools beyond the obvious list-vs-get contrast.

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 no guidance on when to use this tool over alternatives like wealthbox.events.get or wealthbox.events.create. It simply says 'List events' with no context about typical use cases, prerequisites, or exclusions.

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