mtrkr_prism_positions

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

No annotations are provided, so the description carries full burden. It states it fetches on-chain data from the Prism NFT Position Manager, indicating a read-only operation. However, no mention of potential side effects, rate limits, or authentication requirements, leaving gaps in behavioral understanding.

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 sentences, no filler. First sentence states purpose and return fields, second sentence adds data source. Perfectly front-loaded and efficient.

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 simple one-parameter tool without an output schema, the description is fairly complete. It lists key return fields (token pairs, tick ranges, etc.) and data source. However, lacking output schema means agent must infer exact structure, and no mention of pagination or limits for multiple positions.

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 coverage is 100% for the single parameter 'address', with a description already provided. The tool description adds minimal value beyond confirming the parameter is a wallet address or .mega name, which is redundant with the schema. No additional semantic detail is given.

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?

Description clearly states the action (get), resource (concentrated-liquidity LP positions on Prism DEX), and scope (for a wallet). It lists specific returned data (token pairs, tick ranges, etc.), distinguishing it from sibling tools like mtrkr_lp_positions as it's specific to Prism DEX.

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 implies use when querying LP positions on Prism DEX for a wallet, but does not explicitly state when to use or when not to use this tool versus alternatives like mtrkr_lp_positions. No exclusion criteria or contextual examples are provided.

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