applications.complete_document_uploadVerify the uploaded object, content signature, session ownership, expiry, and exact application version before creating the protected document record.
| Name | Required | Description | Default |
|---|---|---|---|
| sessionToken | Yes | ||
| idempotencyKey | Yes | ||
| expectedVersion | Yes | ||
| uploadSessionId | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | ||
| status | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate write operation (readOnlyHint=false), idempotent (idempotentHint=true), non-destructive. The description adds context by specifying the verification checks (object, content signature, session, expiry, version) and the subsequent record creation, which goes beyond 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?
Single sentence with a clear verb-first structure. Every word is necessary, and the sentence is well-organized to convey the sequence of verifications and the final action.
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?
With an output schema present, return value explanation is not required. However, given 4 required parameters and no schema description coverage, the description should provide more context on parameter roles. It covers the tool's purpose but leaves parameter semantics incomplete.
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 0%, yet the description provides no explanation of individual parameters like sessionToken, idempotencyKey, expectedVersion, or uploadSessionId. The tool-level description does not compensate for missing parameter documentation.
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's action ('verify' then 'create') and resource ('protected document record'). It distinguishes from siblings like create_document_upload and upload_document by emphasizing the verification steps.
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 implies this is the final step after uploading a document, but it lacks explicit guidance on when to use this versus alternatives like create_document_upload or upload_document. No when-not-to-use or alternatives are mentioned.
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.