calculate_auto_entrepreneur

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

With no annotations, the description provides basic insight into the tool's function (non-destructive calculation) and output structure, but lacks details on side effects, rate limits, or assumptions.

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?

Two concise sentences: the first states purpose and output, the second references related tools. Front-loaded with key information, no redundant words.

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?

For a simple calculator, the description covers purpose, inputs, and outputs. Output schema exists (not shown but listed), making the description self-contained. Reference to bundle aids discoverability.

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%, and the description adds overall context, but does not significantly enhance parameter meaning beyond what the schema already provides (e.g., revenue is annual, category enum).

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 calculates net income and social charges for French auto-entrepreneurs, lists output fields, and references a bundle for related calculators, effectively distinguishing it from siblings.

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 implies usage for auto-entrepreneur calculations and mentions a related bundle, but does not explicitly contrast with similar tools or provide exclusions. The context is clear but not directive.

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