Prepare Form BE 2025 draft

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

The description adds valuable behavioral facts beyond the annotations: 'never stores data or submits to MyTax', 'output remains review-gated', and 'source-linked'. These details align with readOnlyHint=true, idempotentHint=true, and destructiveHint=false, with no contradiction.

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 two concise sentences with the core action front-loaded and the safety/review constraints stated immediately after. No filler or redundant 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 11 parameters, nested objects, no output schema, and low schema coverage, the description covers the tool's purpose and constraints but leaves out guidance on how to structure the inputs or what the returned draft will contain. It is adequate for selection but not fully complete for invocation.

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 low at 18%, so the description must compensate for undocumented parameters, but it only generically references 'taxpayer inputs' and 'relief evaluation'. It does not explain required fields like assessmentType or income, or clarify the meaning of the many nested objects.

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 the specific verb 'Compile' and names the resource 'Form BE fields', with clear inputs ('reviewed taxpayer inputs and a deterministic TaxBrain relief evaluation'). It also distinguishes itself from the sibling tools, which are about tax authority releases and readiness assessment, by focusing on draft preparation.

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?

The description clearly implies the tool should be used after inputs have been reviewed and after a deterministic TaxBrain relief evaluation exists. It does not provide explicit exclusions or name alternatives, but the context signals and sibling list make the intended usage reasonably clear.

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