Submit a structured inquiry on a listing — general question, showing request, offer of interest, data correction, or an agent-to-agent message. Requires a registered Trellistate agent API key.
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | ||
| listing_id | Yes | Public listing ID. | |
| inquiry_type | No | general | |
| contact_email | No | ||
| structured_payload | No | Machine-readable payload other agents can parse (e.g. {"preferred_date":"2026-06-12"}). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=false already indicates a write operation, and the description adds the authentication requirement ('Requires a registered Trellistate agent API key') and lists supported inquiry types. It does not disclose side effects, response format, or rate limits, but given the annotation covers mutation, this is adequate.
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 a single, front-loaded sentence that conveys the core purpose and key inquiry types without redundancy. Every phrase earns its place and the structure is efficient.
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 tool has 5 parameters (including a nested object), no output schema, and only a readOnlyHint annotation. The description covers the action, inquiry types, and auth requirement, but omits details about expected responses, optional parameter relationships (e.g., contact_email when inquiry_type is showing_request), and whether structured_payload is required for certain types. This leaves gaps for an agent invoking the tool.
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 only 40% (listing_id and structured_payload have descriptions, while message, inquiry_type, and contact_email do not). The description compensates partly by enumerating the inquiry_type enum values, but it does not explain the semantics of message or contact_email, so the added value is limited.
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 verb ('Submit') and resource ('a structured inquiry on a listing'), and enumerates inquiry types (general, showing request, offer of interest, etc.). This differentiates it from sibling read-only tools like get_listing and search_listings.
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 usage context: it is for submitting inquiries, while siblings retrieve listings/agents. It also mentions the prerequisite of a registered Trellistate agent API key. However, it does not explicitly contrast with alternatives or state when not to use it, so it falls short of a perfect score.
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.
There is clear overlap between list_recent and search_listings, as search_listings with no filters returns the same recent listings as list_recent. Other tools are distinct, but this redundancy creates ambiguity for an agent choosing between them.
The naming pattern is mostly consistent with verb-first commands: get_listing, list_agents, list_recent, search_listings, submit_inquiry. The minor deviation is list_recent, which omits the object (listings) but remains understandable.
Five tools is well-scoped for a niche service focused on property listings and agent discovery. Each tool except the redundant pair earns its place, and the count is neither too thin nor too heavy.
The set covers the core workflows: discovering and viewing listings, finding agents, and submitting inquiries. A minor gap is the lack of a get_agent_detail tool, but agents can likely work around it, and there are no dead ends in the primary flow.
