business_tax_summary

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Generate' implies a read-only or computational operation, but the description doesn't specify whether this tool requires specific permissions, how it processes data, what the output looks like, or if it has side effects like data storage. For a tool with three required parameters and no annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence with no wasted words, making it easy to parse. It's appropriately sized for a tool with a straightforward name, though it could benefit from more detail given the complexity implied by the parameters.

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 the tool's complexity (three required parameters, nested objects, no output schema, and no annotations), the description is incomplete. It doesn't explain the output format, behavioral traits, or parameter meanings, leaving significant gaps for an agent to understand how to use it effectively in context with other tax and analytics tools.

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%, meaning none of the parameters (entityId, taxYear, financialData with revenue and expenses) are documented in the schema. The description mentions 'comprehensive business tax summary', which hints at the purpose but doesn't explain what each parameter means, their formats, or how they influence the summary. This fails to compensate for the lack of schema documentation.

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 states the tool's purpose as 'Generate comprehensive business tax summary', which includes a verb ('Generate') and resource ('business tax summary'), making it clear what it does at a high level. However, it doesn't distinguish this tool from sibling tools like 'calculate_federal_income_tax', 'calculate_state_taxes', or 'tax_projection_scenarios', leaving ambiguity about its specific scope or output format compared to alternatives.

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 provides no guidance on when to use this tool versus other tax-related tools in the sibling list, such as 'calculate_federal_income_tax' or 'tax_planning_strategies'. It lacks explicit instructions on prerequisites, context, or alternatives, leaving the agent to infer usage based solely on the tool name and description.

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