Buzzedin

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

Annotations already declare a safe, non-destructive, non-open-world operation, and the description adds real behavioral context beyond that: the link is consumed on Buzzedin, the user must save it themselves, and the notification arrives via email or push on new matching listings. This clarifies that the tool does not itself subscribe the user, which is the key behavioral nuance. It does not describe what the tool returns (URL shape, whether the link expires).

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?

Three sentences, front-loaded with what is produced and what happens next, followed by the parameter instruction and the trigger condition. No filler. Slightly dense but every sentence carries information.

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 link-generating tool with 56 optional filters, full schema coverage, and annotations covering safety, the description supplies the essential missing context: the destination app, the user action required, and the notification mechanism. The remaining gap is the return value — with no output schema, the description never says a URL string comes back that should be surfaced to the user.

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% across 56 parameters, so the baseline is 3; the description earns above that by instructing the agent to 'pass the same filters used for search_listings,' which prevents re-interpretation of an already-mapped filter set. It does not address any parameter individually or flag whether filters are optional for a valid alert, but the schema handles the per-parameter detail.

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 specific verb and artifact ('create a link that opens this search on Buzzedin') plus the downstream outcome (user saves it as an alert and gets email/push on new matches). It also implicitly separates itself from search_listings by telling the agent to reuse that tool's filters rather than re-deriving them. It stops just short of naming the sibling as a distinct alternative in so many words.

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?

Explicit trigger conditions are given: 'Use it when the user wants to be notified, or accepts the offer of an alert.' The implied complement — use search_listings to actually search — is supported by 'Pass the same filters used for search_listings.' No explicit when-NOT conditions or edge cases (e.g., user already has an alert, missing filters) are covered.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real context the schema cannot: the source set, the hard cap of 8 results, the deal-score/neighborhood-median enrichment, and the explicit caveat that enrichment is estimated and details must be confirmed on the listing.

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?

Front-loaded with purpose and sources, then returns, then the next-page note. It is dense but every sentence carries information; the only mild weakness is that the filter enumeration and return-value description run together in one long block.

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 57-parameter tool with nested objects and no output schema, the description covers what an agent most needs: what is searched, what comes back (count cap, deal score, median comparison, features, detail link), the estimate caveat, and pagination behavior via the page note.

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 57 richly documented params, so the baseline is 3. The description adds value only at a category level (price, bedrooms, neighborhoods, commute, amenities, rent-stabilized, lease takeovers), and does not clarify the genuinely tricky distinctions such as rentControlledClaimed vs rentControlledVerified or poiCommuteFilters vs commuteFilter — those live only in 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?

States a specific verb and resource ("Searches active NYC rental listings") plus the exact data sources (StreetEasy, LeaseBreak, NYBits, Reddit, building sites, Buzzedin) and the supported filter universe. An agent immediately knows what this tool does and that it is a listing search, not an alert/notification tool like the sibling.

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 gives one useful operational cue — "Fetch the next page to see more results" — and the filter enumeration signals when the tool fits. However it never names the sibling create_alert_link or explains when to route to alert creation instead of searching, so the search-vs-alert decision is left to inference.

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