get_morpho_positions

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

Description adds valuable behavioral details beyond annotations: auto-discovery performance warning, fast path suggestion, and return content. Annotations already indicate read-only, idempotent, non-destructive; description enriches with operational nuance.

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?

Three sentences efficiently convey purpose, key behavioral nuance, and return content. No redundant or superfluous text.

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?

Given no output schema, the description clarifies return categories (supplied/borrowed assets and collateral) per market. Lacks output format specifics but adequate for a query tool. No mention of limits or pagination.

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 covers 100% of parameters with descriptions; tool description adds context about marketIds auto-discovery vs explicit fast path. However, the wallet parameter schema description uses 'execute this action' which slightly misaligns with the read-only nature.

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 identifies the tool as fetching Morpho Blue positions for a wallet, specifying the resource (Morpho Blue) and action (fetch). It distinguishes from sibling tools like get_compound_positions by explicitly naming the protocol.

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 advises on when to use explicit marketIds for speed versus omitting them for auto-discovery, but does not explicitly contrast with sibling tools for mutations (e.g., prepare_morpho_*). The readOnlyHint annotation reinforces the read-only nature.

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