pm_buy

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full responsibility. It only states the action with no disclosure about side effects, transaction requirements, or operational constraints like market availability or fee structures.

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?

Extremely short phrase, but under-specified. It is not a full sentence and lacks critical details; brevity here sacrifices usefulness.

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 three required parameters and no output schema, the description fails to provide essential context such as what constitutes a market identifier, how outcomes are numbered, or the currency unit for amount_usdb. The tool is part of a complex private market system, and the description is grossly insufficient.

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 input schema has 0% description coverage, and the description adds no explanation for any of the three required parameters (market, outcome, amount_usdb). The agent gets no context about their format, allowed values, or units.

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?

Clearly states the action (buy), resource (shares), and context (private market outcome). Distinguishes from generic buy tools, but does not explicitly differentiate from similar sibling tools like pm_buy_order or pm_buy_multiple_orders.

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 guidance on when to use this tool versus alternatives. Does not mention prerequisites, typical usage scenarios, or provide any hints about when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.