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

Annotations already declare readOnlyHint=true, so the safe-read nature is known; the description usefully adds the returned fields (asset, units, owner, last activity heights). It does not address the unusual idempotentHint=false, pagination, or any limits on how many accounts are returned, so it adds only moderate value.

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?

Two tight sentences, no filler, with the core behavior front-loaded and the return payload described second. Every clause earns its place.

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?

No output schema exists, so the description's enumeration of returned fields is genuinely needed and partially compensates. It is nearly complete for a simple one-param read, with the only real gap being sibling disambiguation and pagination behavior.

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 a single parameter at 100% schema description coverage, the schema already fully documents 'address'. The description merely restates that the lookup is address-scoped and adds no format, normalization, or validation detail beyond the 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?

States a specific verb and resource ('Returns all trade account positions') scoped to a specific address, so the agent knows exactly what is fetched. However, it never distinguishes itself from close siblings like list_trade_accounts or get_trade_unit, leaving the plural-vs-single distinction to inference.

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 phrase 'for a specific address' hints at address-scoped lookup, but there is no explicit when-to-use statement, no mention of when to prefer list_trade_accounts, and no prerequisites. The agent gets no routing guidance beyond the name.

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