get_buy_deadline

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

With no annotations, the description carries full burden. It discloses the T+2 settlement rule and the special return string. It does not specify output format (e.g., date format) but adequately conveys the behavior for a simple query 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 two sentences, front-loaded with the main purpose, and includes the alternative outcome. No extraneous words; 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?

Given the tool's simplicity (one parameter, no output schema), the description covers core functionality and edge case. It could specify the output format (e.g., date string) but is otherwise complete.

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 single parameter 'symbol' is implied in the description as a stock ticker. The description adds meaning by explaining it must be in the PSX payouts table. With 0% schema coverage, the description compensates well.

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 returns the last buy date for a symbol with an upcoming dividend, applying T+2 settlement. The verb 'return' and resource 'buy deadline' are specific, and the tool is well-distinguished from siblings like get_upcoming_dividends and get_dividend_history.

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 specifies the tool is for symbols with upcoming dividends and details the 'no upcoming dividend' case. However, it does not explicitly contrast with siblings like get_dividend_history or screen_dividend_stocks, leaving some implicit guidance.

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