uw_earnings

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

Annotations declare readOnlyHint, which is consistent with 'access' and 'get'. However, the description lists actions that would require parameters (e.g., date, ticker) but the schema has no properties, creating a behavioral inconsistency that undermines trust.

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 uses a bullet list for actions, which is structured. However, the content is misleading due to the missing parameters, making it less efficient.

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?

Without parameters or output schema, the description is incomplete. The three actions imply different input requirements, but none are defined, leaving the agent without enough information to use the tool correctly.

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 coverage is 100% but the schema is empty. The description mentions actions that would typically need parameters but offers no way to pass them. This adds no value and confuses the agent.

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 states it accesses UnusualWhales earnings data and lists three actions (premarket, afterhours, ticker), which gives a general idea. However, the lack of parameters in the input schema contradicts the implied need for date or ticker inputs, reducing clarity.

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 siblings like uw_stock or uw_screener. There's no mention of prerequisites or context for each action, leaving the agent to guess.

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