Create a portfolio draft

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

Discloses that it is draft-only, never changes live positions, requires OAuth write:drafts scope and Bullrun Pro account. This adds significant context beyond the annotations, which only indicate non-read-only and non-destructive.

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?

The description is relatively long but well-structured with key points front-loaded. Every sentence adds value, though it could be slightly more concise without losing information.

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 3 parameters, 100% schema coverage, and no output schema, the description covers prerequisites, behavior, interaction, and expectations. It is complete enough 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%, so baseline is 3. Description adds extra context: explains that omitting prompt triggers user elicitation, and provides default values for maxPositions and startingCash. This adds value 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?

The description clearly states the tool's purpose: building or proposing a brand-new portfolio by generating a reviewable draft. It uses specific verbs like 'BUILD' or 'PROPOSE' and distinguishes it from create_position_draft, which handles additions to existing portfolios.

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?

Explicitly says when to use (user wants a new portfolio) and when not to (use create_position_draft for existing portfolios). Provides guidelines for vague briefs, including asking one round of multiple-choice questions with defaults.

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