wealthbox.notes.list

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only lists query parameter names without explaining pagination behavior, response format, date semantics, or authentication requirements. This leaves critical operational behaviors undisclosed.

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, front-loaded sentence that efficiently states the purpose and lists parameters. It is free of fluff and easily scannable, though it sacrifices necessary detail for brevity.

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?

The tool has no annotations, output schema, or parameter descriptions. The description only provides parameter names, leaving an agent without sufficient information to construct the query object, interpret date values, or understand pagination behavior. This is notably incomplete for a list operation with four parameters.

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?

With 0% schema description coverage, the description must compensate by explaining each parameter. It repeats the names (updated_since, updated_before, page, per_page) but gives no meaning, format, defaults, or constraints. This adds minimal value over the bare schema.

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 uses a specific verb and resource ('List notes'), clearly indicating a collection-list operation. It distinguishes from sibling tools like notes.get, notes.create, and notes.update, which are single-item or mutation operations. The resource name 'notes' disambiguates from other list tools for different entities.

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 versus alternatives. It does not mention any selection criteria, filtering scope, or situations where notes.get or other list tools would be more appropriate. An agent is left without contextual direction.

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