Create Furniture

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

The description adds context beyond the destructiveHint annotation by mentioning automatic depreciation calculation and default periods for new and second-hand furniture. However, it does not disclose potential impacts on financial reports or irreversible nature of the 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 concise at three sentences, providing core purpose and key behavior without superfluous text. Could be better organized but is efficient.

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?

Given the complexity (8 parameters, no output schema, no param descriptions in schema), the description is insufficient. It lacks details on return value, error handling, and full behavioral scope.

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?

With 0% schema description coverage and 8 parameters, the description only covers amount, duration_years defaults, and is_second_hand impact. Missing explanations for tva_rate, is_dedicated, purchase_date format, and other parameters.

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 creates a depreciable furniture item for an LMNP property, distinguishing it from siblings like list_furniture, update_furniture, and delete_furniture. It also provides specific details about amount in euros and default depreciation period.

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 creating furniture items but does not explicitly state when to use this tool versus alternatives like list_furniture or update_furniture. It also lacks prerequisites (e.g., property must exist) or exclusions.

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