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

With no annotations, the description carries the full burden. It discloses the data source (8-K filings), that events are 'ranked', and that each includes a link, which is meaningful behavioral context. However, it says nothing about return format, ranking methodology, or pagination/limits for the days window.

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?

Front-loaded with the core resource and the event taxonomy, followed by a short disclaimer. The event list is long but informative, and there is essentially no filler.

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?

The description thoroughly covers what data is returned but, with no output schema and no annotations, it leaves return structure, ranking output shape, and the required ticker parameter undocumented. Adequate for content discovery but incomplete for correct invocation.

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 description mentions no parameters at all. Schema coverage is only 50% (ticker has no description, days only gives a numeric range), and the description does nothing to compensate by explaining ticker format or the meaning of the days window.

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 a specific verb+resource ('Material corporate events from SEC 8-K filings') and enumerates the exact event types returned. It clearly distinguishes this tool from siblings like wallstreet_financials, wallstreet_insider_trades, and wallstreet_yield_curve without requiring the agent to open any schema.

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 content scope implies when the tool is useful (tracking material corporate events), but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as wallstreet_company_brief. Usage must be inferred from the data coverage rather than stated.

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