run_projection

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

No annotations provided, so description carries full burden. Discloses deterministic behavior, always starts at session plan's startYear, details of tax modeling (federal, state, local, override), and consistency with web app output. Comprehensive.

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?

Description is somewhat long but well-structured: disclaimer first, then core action, parameter details, tax modeling. Every sentence adds value. Could be slightly more concise.

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?

No output schema exists. Description partially explains return values for summary and years, but lacks full structure of per-year ledger. With moderate complexity, a bit more detail on output format would improve completeness.

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. Description adds meaning beyond schema by explaining default behavior and what each enum value returns (summary vs years). Provides context on startYear/endYear/summary/caveats vs per-year ledger.

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 it runs a deterministic projection on the session plan. It distinguishes from siblings like build_plan (to change start year) and solve_max_spending (optimization). Provides specific verb, resource, and constraints.

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 states educational decision-support only, not advice, and warns against prescribing securities actions. Explains when to use build_plan to change startYear. Could be more explicit about when not to use vs other siblings like compare_scenarios.

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