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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds the meaningful constraint that the window is limited to up to 7 days and that no ticker is required, but says nothing about pagination behavior or result ordering beyond 'most recently filed'.

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?

A single compact sentence that front-loads the core capability (most recently filed material events) before the scoping constraints. Nothing is wasted, though it is terse enough that it omits context it could afford to include.

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?

For a read-only list tool with full schema coverage and no output schema, the description covers what the tool returns at a high level (most recently filed events across all companies). The main gap is the absence of guidance on choosing this tool over its list/get siblings.

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%, so all six parameters are documented in the schema, making 3 the baseline. The description only loosely gestures at two of them (minutes via 'minute window', ticker via 'no ticker required') and adds no syntax or enumeration detail beyond 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?

The description names a specific verb (list) and resource (material events) plus a scope qualifier: most recently filed, all companies, minute window. It distinguishes itself from a ticker-scoped listing by stating 'no ticker required'. It does not explicitly name siblings like events_list or events_get, so it falls short of a 5.

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?

Usage is implied rather than stated: an agent can infer this is the tool for a recent cross-company feed without a ticker. However, no alternatives are named (events_list, events_get) and no explicit 'use this when' condition is given, so guidance is only implied.

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