yield_alert_check

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

No annotations provided, so description carries full burden. States it uses cached data, is non-destructive, and returns specific fields. Does not mention error handling or authentication, but for a simple read-only tool, it's fairly transparent.

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?

Very concise at 4 sentences; front-loaded with the core action. Every sentence adds value: polling action, freeness, caching, return fields. No redundant information.

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 simplicity of the tool (1 param, no nested objects) and presence of output schema, the description covers the essential: what it returns and that it's safe. Minor missing details on error states, but not critical for a poll 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 description coverage is 100%, and the input schema already provides clear meaning for 'alert_id' with context ('Alert ID from yield_alert_set' and example). The description adds no additional parameter semantics beyond what is in the schema.

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?

Description clearly states it polls yield alert status, using specific verb 'poll' and resource 'yield alert'. Distinguishes from siblings like yield_alert_set (create) and yield_alert_delete (delete) by focusing on status checking.

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?

Explicitly says 'FREE' and 'Safe to call frequently', guiding the agent on when to use (frequent polling). Does not explicitly state when not to use, but context from sibling tools implies it's for status checks only.

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