marge_chantier

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the calculation formula and required API permissions, which is useful context, but omits whether the operation is read-only, the time period covered, and error behavior.

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 tightly written sentences with no filler. The purpose, formula, and prerequisite permission are front-loaded and easy to scan.

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 calculation tool with no output schema, the description covers the formula and permission requirement. However, it omits the time period for revenue and expenses and the return format, which are important for correct interpretation of the margin.

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% with one parameter. The description adds meaning by saying the chantier is identified 'par son numéro dans le compte', partially compensating for the lack of schema detail, but does not clarify format, range, or whether it matches the internal integer ID.

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?

States clearly that it computes the margin for a construction site, defined as billed revenue minus expenses. The resource and calculation are specific, though it does not explicitly differentiate itself from sibling tools like chantier or depenses.

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?

Provides only a permission prerequisite ('Nécessite une clé avec les permissions factures + dépenses') but no guidance on when to use this tool versus alternatives like chantier or factures. The agent must infer usage from the name and purpose alone.

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