brrrr_analysis

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, establishing a safe read operation. The description adds value beyond annotations by listing the returned outputs (e.g., BRRRR Score, cash flow), providing clarity on what the tool produces. No contradictions or missing behavioral traits like rate limits.

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 (27 words) that front-loads the tool's purpose and enumerates key outputs. Every word adds value, and there is no redundancy or filler.

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?

Despite 20 parameters and no output schema, the description only lists outputs without explaining how inputs influence results, assumptions, or data sources. For a complex analysis tool, this is insufficient for an agent to fully understand the tool's behavior.

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 has 100% description coverage, so the schema already documents each parameter. The tool description does not add any new parameter information beyond what the schema provides. Baseline score of 3 is appropriate.

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 analyzes a BRRRR real estate deal and lists specific outputs (e.g., all-in cost, ARV margin). The verb 'Analyze' and the resource 'BRRRR real estate deal' are specific. However, it does not differentiate from siblings like 'investment_property_analysis', missing an opportunity to clarify scope.

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 the tool is used for BRRRR deal analysis but provides no explicit guidance on when to use it vs. alternatives (e.g., 'investment_property_analysis'). No exclusions or context are given, relying on the user to infer applicability.

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