Create Property

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

The annotation destructiveHint=true indicates mutation, and the description confirms creation. It adds unit details for monetary and area fields but lacks info on validation, permissions, side effects, or return values beyond basic action.

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 brief (3 sentences) and front-loaded with the main action. It conveys key details efficiently, though some organization could improve scannability.

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?

With 19 parameters, 3 required, and no output schema, the description covers the main action and critical field units but omits what the tool returns (e.g., created property ID) and lacks detail on required fields beyond listing units for some.

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 description explains units for acquisition_price, notary_fees, market_value, total_area, rented_area and lists valid values for type, rental_type, and tva_regime. However, with 0% schema description coverage and 19 parameters, many (e.g., city, address, notes) remain unexplained.

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 'Crée un nouveau bien immobilier LMNP pour l'utilisateur connecté.' This is a specific verb+resource (create property) with domain context (LMNP). It differentiates from sibling tools like get_property, list_properties, and update_property.

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 when the user wants to add a new property but does not explicitly state when to use this tool versus alternatives like update_property. No exclusions or prerequisites are mentioned.

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