contracts.get_signing_linkReturn a secure signing URL only when the active signer invitation email matches the email-verified application session. Human verification, review, and signature remain in the signing flow.
| Name | Required | Description | Default |
|---|---|---|---|
| sessionToken | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | ||
| status | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value beyond annotations by noting that human verification, review, and signature remain in the signing flow, indicating the tool does not complete the process. It also mentions the email matching condition. Annotations already indicate read-only and idempotent, so the description clarifies the logical guard.
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 consists of two short, clear sentences. Every word serves a purpose, no fluff. The key information is front-loaded.
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?
The description covers the core logic and condition but lacks explanation of the parameter. Given the presence of an output schema (though not shown), the return value is presumably documented elsewhere. The description is mostly complete for a simple tool, but the parameter gap reduces completeness.
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?
With 0% schema description coverage, the description should explain the 'sessionToken' parameter but only implies it relates to the application session. The token's format, origin, or role is not explicitly described, leaving ambiguity for the AI agent.
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 clearly states the tool returns a secure signing URL under a specific condition (email match). It uses a specific verb ('Return') and resource ('signing URL'), and distinguishes itself from sibling tools which deal with applications, bookings, payments, etc.
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 provides clear context by specifying the condition for use (matching emails and verified application session), but does not explicitly state when not to use or mention alternative tools. The guidance is adequate but lacks exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool is clearly scoped to a distinct action within its domain (applications, viewings, rentals, etc.). Verbs like start, update, submit, create, propose, accept are unambiguous and non-overlapping.
All tools follow a consistent domain_verb pattern in snake_case (e.g., applications.start, rentals.search, viewings.propose_availability). No mixing of styles.
21 tools cover a broad rental lifecycle (discovery, applications, quotes, viewings, payments, contracts). While slightly above the typical 15-tool sweet spot, each tool has a defined purpose and no redundancy.
The lifecycle from rental search to booking confirmation and contract signing is well-covered. Minor gaps exist (e.g., no explicit cancellation or withdrawal tools), but the core flows are complete.