Analyze portfolio net per available night

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

With no annotations provided, the description carries the full burden. It explicitly states 'Read-only — never changes any prices', which is a critical behavioral trait. It also explains parameter defaults. More details on authentication or rate limits are not necessary for this simple analytical tool.

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, consisting of three to four sentences. It front-loads the key identity ('The margin guard for Wheelhouse pricing') and immediately explains what it computes. Every sentence adds information, though the first sentence could be more explicit.

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 no output schema, the description lists the specific outputs (net per available night, leak, best/worst properties), setting expectations. For a tool with three optional parameters and a well-defined purpose, the description is fairly complete and covers the essential aspects.

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 coverage is 100% with each parameter having a description. The description adds value by clarifying the default window behavior for from/to and explaining avg_turnover_cost as an override in € per turnover, providing context beyond the schema.

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 verb 'computes' and the resource 'short-term rental portfolio's net after turnover costs', listing specific outputs (net per available night, leak, best/worst properties). It distinguishes itself from siblings like set_target and apply_decision by emphasizing its read-only analytical nature.

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 clear context: it is read-only and never changes prices, with optional from/to parameters defaulting to last 30 + next 90 days. It does not explicitly list when not to use it or alternatives, but the context of sibling tools and the described function imply appropriate usage.

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