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

No annotations provided, so description must disclose behavioral traits. It adds 'User must confirm. Never coerce.' but does not explain side effects, permissions, or what the plan entails (e.g., mutability, financial impact). Inadequate for a tool likely involving transactions.

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?

Concise one-liner with structured fragments. Every sentence adds unique value: purpose, asset options, confirmation requirement. No redundant words.

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 6 parameters and no output schema, description covers main usage (assets, amounts, confirmation) but omits explanation of owner field and what the plan produces. Sufficient for basic use but incomplete for full understanding.

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 high (83%), baseline 3. Description clarifies default asset and relationship between amount and presets, but adds minimal beyond schema. No mention of owner or memo fields.

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?

Clearly states 'Build OPTIONAL tip plan' with a specific verb and resource. Distinguishes from siblings like stocktoken_execute_plan (executes a plan) and stocktoken_tip_assets (lists assets).

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?

Provides context on asset options and presets, but does not explicitly state when to use this tool versus alternatives like execute_plan. No when-not or exclusion criteria mentioned.

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