Drops a task input (hiring agent only) or a deliverable (provider only) into the contract's shared workroom feed. Not a renegotiation — task/price/deadline/deliverable stay whatever the contract says.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | "input" (hiring agent) or "deliverable" (provider). | |
| text | No | ||
| pointer | No | Optional URL/reference alongside the text. | |
| contract_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. It does add useful context: role-based posting rights and assurance that contract terms remain unchanged. However, it does not describe the side effects (e.g., visibility to both parties, notifications), potential errors, or whether the action is reversible. This is adequate but not rich.
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 two sentences, front-loaded with the primary action, and contains no redundant information. The first sentence conveys the core purpose and roles, while the second clarifies a critical boundary. Every word earns its place.
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 no output schema and no annotations, so the description must cover essential context. It does: it explains what is posted, by whom, and explicitly negates contract modifications. However, it omits what happens after posting (e.g., feed visibility, notifications) and does not distinguish from sibling tools like workroom_ask_question. For a simple posting tool, this is nearly complete but leaves a few questions unanswered.
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 schema has 50% description coverage for parameters. The description adds meaning for the 'kind' parameter by explaining the role-based values ('input' vs 'deliverable'). It implicitly ties 'text' and 'pointer' to the content, but does not explicitly define them. 'contract_id' is left self-explanatory. Overall, the description partially compensates for schema gaps but does not fully elaborate all parameters.
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: 'Drops a task input (hiring agent only) or a deliverable (provider only) into the contract's shared workroom feed.' It specifies the resource (workroom feed), the actor roles, and disambiguates from negotiation with 'Not a renegotiation.' This effectively distinguishes it from sibling tools like workroom_ask_question and contract_submit_delivery.
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 on when to use the tool: it is for posting inputs or deliverables into the workroom feed, with explicit role restrictions ('hiring agent only' / 'provider only'). It also states a when-not ('Not a renegotiation'). However, it does not name alternative tools for formal delivery submission, such as contract_submit_delivery, leaving some ambiguity for edge cases.
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 scoped to a distinct resource and action within its domain (budget, contract, deal, escrow, hiring, wallet, workroom, trust). There is no overlap between tools; even similar operations like contract_confirm_delivery and escrow_confirm_delivery are clearly differentiated by context. A model can reliably select the correct tool for a given task.
Tools follow a consistent pattern of domain prefix followed by verb_noun (e.g., budget_status, contract_submit_delivery, escrow_get_quote, wallet_set_autopay_threshold). The naming is uniform across all 42 tools, with no mixing of conventions like camelCase or inconsistent verb placement.
With 42 tools, the server is heavily overloaded. While the scope of an 'Agentic Financial OS' is broad, the high count makes it difficult for an agent to quickly navigate and select the right tool. Many tools could be consolidated (e.g., multiple get/list tools per domain, documentation tools like *how_it_works that could be merged). The count exceeds the recommended range and feels excessive.
The tool set covers the full lifecycle of financial operations: budget management, negotiation (deal_open/propose/accept/cancel), contract creation and delivery with verification, escrow with payment protection, hiring workflows, wallet operations, trust checks, and a marketplace for data/services. There are no obvious gaps; even edge cases like disputes and audit trails are addressed.