payments.get_statusReturn due and received payment truth for the scoped application. An approved human-action URL is returned only from an exact, unexpired provider session; no authorization URL is fabricated.
| 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?
Description adds behavioral context beyond annotations: it specifies that a human-action URL is only returned from an exact, unexpired provider session and that no URL is fabricated. This complements the readOnlyHint and idempotentHint annotations, clarifying important constraints.
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?
Two sentences with no redundant phrasing. The primary purpose is front-loaded, and the secondary behavioral detail is efficiently provided. Every sentence adds value.
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 simple read-only tool with a single parameter and a clearly named output schema, the description is mostly complete. It lacks error conditions or prerequisites beyond the session, but the annotations and output schema fill many gaps. A brief note on when sessionToken expires would improve 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?
Schema coverage is 0%, yet the description provides no explanation of the sessionToken parameter. The parameter name is somewhat self-explanatory, but the agent lacks guidance on how to obtain or format a session token, which is critical for correct invocation.
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?
Description clearly states the tool returns 'due and received payment truth for the scoped application', which is specific and distinct from sibling tools like applications.get_status or reservations.get_status. The purpose is evident and unambiguous.
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?
No explicit when-to-use or when-not-to-use guidance is provided. However, the name and title imply usage for first-payment status. The description does not differentiate from alternatives like bookings.get_confirmation or quotes.get, but the payment-specific scope provides implicit guidance.
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.