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

With annotations declaring idempotentHint, non-destructive, and not read-only, the description adds valuable behavioral context: the request is accepted by staff before research starts, involves VA verification and Alexander's judgment, and returns only a continuation link. It also clarifies that no email is sent, which is not indicated by annotations. No contradiction with 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 description is compact – two sentences that front-load the core action and then set expectations. It is informative without being verbose, though it could be slightly more structured to separate the action from the limitations.

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?

Given a tool with 15 parameters and an output schema, the description provides a clear workflow and expected behaviors. The schema fully documents parameters, and the description covers the submission lifecycle. A minor gap is not mentioning how to retrieve the eventual report (via get_research_request), but that is not required for invoking this tool correctly.

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 for all 15 parameters, including detailed semantics for request_key, consent, and shortlist_token. The description adds no parameter-level meaning, which is acceptable given that the schema already fully documents them. Baseline 3 applies.

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 action – Submit a saved shortlist and renter brief – with a clear target (Taco Street) and outcome (private continuation link). It differentiates from siblings like create_shortlist (which creates a shortlist) and get_research_request (which retrieves status) by focusing on submission initiation.

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 clear context: it requires consent, refers to a saved shortlist (implying prior use of create_shortlist), and explicitly lists exclusions (no immediate report, no tours, no email). However, it does not name alternative tools for follow-up, such as get_research_request, leaving some inference to the agent.

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