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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful model mechanics (5-year deferral, 10%/30% step-up, 10-year exclusion capped at year 30), but it does not state modeling assumptions, unit conventions, or what the comparison result looks like.

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 definition is a single front-loaded sentence with no wasted words. However, its brevity comes at the cost of missing information, so it is efficient but under-specified rather than fully optimized.

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?

This is an 8-parameter calculator with no schema descriptions and no output schema, and the description does not compensate for those gaps. An agent would not know how to set invest_date, discount_pct, or rate_later_pct, nor what the tool returns.

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 description coverage is 0% across 8 parameters, so the description must carry the meaning of names like gain, rural, growth_pct, hold_years, invest_date, discount_pct, rate_now_pct, and rate_later_pct. It only indirectly hints at rural step-up and hold-period concepts and leaves several parameters entirely unmapped.

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 uses a specific verb ('Models') and a specific resource ('OZ 2.0 investment ... against paying tax now'), which is clear enough for an agent. It does not explicitly distinguish this calculator from siblings such as calc_2026_inclusion or calc_180_day_deadline, so it falls short of a 5.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which sibling calculator is the alternative. The comparison framing ('against paying tax now') implies a use case, but the agent must infer the selection criteria from the title and description alone.

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