calculate_housing_aid

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

With no annotations provided, the description must fully convey behavioral traits. It only states 'Estimate' without detailing calculation assumptions, accuracy, or regulatory context. It does not disclose that the tool applies French rules, uses specific zone definitions, or that results are approximate.

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 concise sentence stating purpose and return format, with no redundant information. It is front-loaded with the key verb and resource.

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 with three parameters and an output schema, the description covers the basic purpose and output. However, it lacks usage guidance and behavioral context, making it minimally adequate for an agent to select and invoke correctly.

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?

The input schema covers all three parameters with descriptions (rent in euros, city zone enum, household size range). The description adds no additional meaning beyond the schema, which is already 100% covered. A baseline of 3 is appropriate given full schema coverage.

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 specifies the exact tool purpose: 'Estimate French housing aid (APL — Aide Personnalisee au Logement).' It clearly identifies the resource (APL) and action (estimate), distinguishing it from sibling calculators like calculate_housing_loan_comparison or calculate_rent_ratio.

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 alternatives, nor does it indicate prerequisites or limitations. For example, it does not mention that the tool is for French APL only, or that it should not be used for other housing benefits.

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