REP Helper

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

No annotations are provided, so the description carries full disclosure burden. It mentions the property types (STR/LTR) but fails to describe mutation side effects, idempotency, error conditions (e.g., duplicate names), or what the tool returns upon success since no output schema exists.

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?

Two efficient sentences with zero waste. The first sentence front-loads the core action, while the second provides essential domain context about property types. Every word earns its place.

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 100% input schema coverage, the description doesn't need to document parameters further. However, lacking an output schema, the description should ideally mention the return value (e.g., created property ID) or success behavior, which it omits. Adequate but not comprehensive.

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%, establishing a baseline of 3. The description adds valuable domain context by explaining the STR/LTR distinction for the 'type' parameter. However, it doesn't elaborate on the nested address structure or date formats beyond what the schema already provides.

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 states a clear verb ('Add') and resource ('rental property'), and specifies scope ('to the account'). It distinguishes from siblings like update_property and delete_property by specifying 'new' and mentioning the account context, though it doesn't explicitly contrast with 'update_property' for existing properties.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., 'use update_property for existing properties'). No mention of prerequisites such as account requirements or uniqueness constraints on property names.

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