Get rebalancing recommendations

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

With no annotations, description discloses read-only behavior, authentication requirement (HTTP 402 on failure), and filtering condition. Provides enough behavioral context for safe invocation, though rate limits or idempotency are not mentioned.

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?

Four sentences, each concise: purpose, filtering, scope, and auth/behavior. Front-loaded with key action and resource. No redundant or unclear phrasing.

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 tool with 3 parameters and no output schema, description explains return type (actions with type and USD amounts), filtering logic, required auth, and read-only nature. Adequately covers all aspects for an agent to use correctly.

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%, but description adds value by explaining bankroll is 'for Kelly position sizing' and threshold as 'minimum adjustment size in USD', providing context beyond the schema descriptions.

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 specifies verb 'Get', resource 'rebalancing actions', context 'Polymarket wallet positions in active Elon tweet-count markets', and output type 'ADD_MORE or TRIM with USD amounts'. Distinguishes from siblings like get_trading_signals and analyze_portfolio by focusing on concrete actionable rebalancing.

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?

Clearly states when to use: for rebalancing in Elon markets, with threshold filtering. Mentions requirement for PRO API key. However, does not explicitly compare to alternatives like get_trading_signals for when one might prefer signals over actions.

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