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

Annotations mark it as a mutation (readOnlyHint=false, openWorldHint=true), and the description adds meaningful behavior: the alert sends emails only when matches exist, at the user-set frequency, and requires the user's Cotlet API key with app access. The confirmation/reaches-other-people caveats add real value beyond the annotations.

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 core email behavior is stated twice in near-identical wording ('emails you new listings that match, only when there are any' and 'emails you new matching listings at the frequency you set, and only when there are any'). The 'Mashvisor: New Property Alert' prefix duplicates the title. Noticeably padded.

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?

For a 10-parameter mutation with no output schema, the description covers the essential behavioral profile: recurring email, deletion workflow, confirmation requirement, and auth need. It could briefly note that repeated identical alerts are possible or what happens to alert dedup, but it is largely complete.

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 description coverage is 100%, with all 10 parameters documented including enums and defaults, so the schema carries the burden. The description only restates the price range (5,000-5,000,000), which the schema already documents, adding little beyond baseline.

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?

States a specific verb+resource: 'Creates a Property Alert in your account' and clarifies it triggers recurring emails of matching listings. An agent can distinguish this from sibling mashvisor_list_property_alerts. The purpose is clear, though it does not explicitly name the sibling it differs from.

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?

Provides actionable context: there is no delete tool so removal happens in Mashvisor, and it flags that calls should be confirmed with the user each time. It gives clear when-to-use and operational constraints but does not contrast against adjacent alert/saved-home tools.

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