expandResult

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

No annotations are present, so the description must disclose behavioral traits. It only states the action 'Expand' without specifying whether it is a read-only operation, any side effects, required permissions, rate limits, or what gets destroyed. The description is insufficient for understanding the tool's impact.

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 efficient sentence with no wasted words. It conveys the core purpose directly and is appropriately front-loaded.

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?

With 10 parameters, 4 required, no output schema, and no annotations, the description is too brief to be complete. It does not explain the return value, behavior in edge cases, or relationship to prior results, leaving agents with significant gaps.

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 low (30%), and the description only lists parameter names (resultId, section, range, page, continuation) without explaining their meaning, format, or constraints. Parameters like 'item', 'detail', and 'page' are not elaborated, leaving the agent with little understanding beyond names.

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 verb 'Expand', the resource 'prior summary-first result', and the expansion criteria (resultId, section, range, page, or continuation). It implies a specific use case but does not explicitly differentiate from sibling tools, which are all helius-prefixed and likely unrelated in function.

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, no prerequisites, and no exclusions. The description assumes the user already knows the context of 'prior summary-first result' without explaining the scenario.

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