REP Helper

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

Annotations declare readOnlyHint=true, so the safety profile is covered. Description adds 'for the account' scoping and confirms optional filtering behavior. Does not disclose default behavior when no filters are applied (returns all?), pagination cursor logic, or response structure given the lack of output schema.

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 sentences totaling 12 words. First states core purpose, second states optional capability. Zero redundancy, front-loaded with action, no wasted phrases.

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?

Adequate for a simple list operation with 2 optional parameters and read-only annotations. Missing explicit description of return values (list vs object), but the verb 'List' strongly implies a collection return. Sufficient without output schema, though mention of default unfiltered behavior would improve it.

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 has 100% description coverage with complete enum documentation. Description reinforces the optional nature of filtering and repeats the enum values (SHORT_TERM/LONG_TERM), adding marginal semantic value beyond the structured schema. Baseline 3 appropriate given schema carries the load.

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?

Clear verb 'List' and resource 'rental properties' with account scoping. Distinguishes from sibling 'get_property' implicitly through pluralization (list vs get), but does not explicitly differentiate when to use one versus the other.

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?

Implies usage through 'Optionally filter by property type,' indicating when to use the type parameter. However, lacks explicit guidance on when to use list_properties versus get_property for single-property retrieval, and no mention of pagination strategy with the limit parameter.

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