Create Income

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

The annotation indicates destructiveHint: true, but the description adds no behavioral context beyond that. It does not disclose effects like permissions needed, return value, or side effects. The description carries little additional transparency beyond the annotation.

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 (two sentences) with key info front-loaded. No unnecessary words, but could benefit from more structured parameter guidance.

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 12 parameters and no output schema, the description is too minimal. It fails to explain important parameters like property_id, income_date format, or optional fields. The tool's complexity demands more complete documentation.

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, the description only clarifies two parameters (amount in euros, source enum). The other 10 parameters (e.g., property_id, income_date, tva_rate) remain undocumented in both schema and description, which is insufficient for a tool with 12 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 it creates a rental income for an LMNP property, specifying amount in euros and listing allowed sources. However, it does not explicitly differentiate from siblings like create_expense, but the name and context make it clear.

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 minimal usage context (amount in euros, allowed sources) but lacks explicit guidance on when to use this tool versus alternatives (e.g., update_income) or when not to use it. No when-not or alternative information.

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