wealthbox.customFields.list

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It simply states 'List custom fields' with no information on return format, pagination, ordering, or side effects. While a 'list' operation is generally read-only, the absence of explicit safety or completeness guarantees leaves gaps.

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 two words, 'List custom fields', with no redundant content. It is maximally concise and front-loaded, stating the action and resource immediately.

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 zero-parameter, straightforward list operation, the description is minimally viable. However, it lacks any detail about the expected output shape or whether the list is complete, which could be relevant for an agent without prior context. It is adequate but not rich.

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 tool has zero parameters, so the schema is complete. Per the rubric, 0 parameters warrant a baseline of 4, and there is nothing for the description to add beyond what the empty schema already conveys.

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 'List' and identifies the resource 'custom fields' clearly. It distinguishes from sibling list tools by naming a unique resource, leaving no ambiguity about what entity is being listed.

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?

There is no guidance on when to use this tool versus alternatives. It offers no context about typical use cases or exclusions, such as whether it should be used for retrieving custom fields for a specific object vs. other list operations.

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