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

No annotations provided, and the description only states the tool's purpose and return fields. Fails to disclose any behavioral traits like handling of edge cases (e.g., zero revenue), category-specific calculations, or if it is read-only. Limited 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?

Two sentences, front-loaded with purpose and return structure, and a pointer to related tools. No wordiness; every sentence serves a purpose.

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?

Covers the main aspects: what it calculates, return fields, and reference to related calculators. Could be improved by explaining the impact of different categories (vente, service_bic, etc.). Good given the tool is straightforward and has an output schema.

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?

Input schema (100% coverage) already describes both parameters adequately. Description adds no additional meaning or context beyond listing return fields, so baseline score of 3 is appropriate.

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?

Clearly states it calculates auto-entrepreneur net income and social charges, and lists return fields. Implicitly distinguishes from siblings via reference to 'finance-france' calculators, but no explicit differentiation.

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?

Implies use for auto-entrepreneur calculations but provides no explicit when-to-use or when-not-to-use guidance. References list_bundles for related tools, but no direct alternatives or exclusions.

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