buy_stock_market

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Places a market buy order,' omitting details about execution guarantees, funds requirements, cancellation, or response behavior. The description is too minimal for a mutation tool.

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 very short and front-loaded, using two lines for purpose and args. It is appropriately sized for a simple order tool, though it could add more context without becoming verbose.

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?

Given the existence of an output schema and sibling tools, the description is incomplete. It does not explain return values, error conditions, or how the order is processed. The agent lacks critical information to handle the tool's response.

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 no descriptions (0% coverage). The description lists parameters with examples ('AAPL'), adding basic meaning beyond the raw schema. However, it does not provide constraints or format details, giving only minimal value.

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 'Places a market buy order for a stock,' using a specific verb (places, buy) and resource (stock). It distinguishes from sibling tools like buy_stock_limit (limit order) and sell_stock_market (sell), indicating a market buy order.

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 no guidance on when to use a market buy order versus limit orders or other alternatives. It does not mention prerequisites, order types, or execution conditions, leaving the agent without usage context.

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