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

With no annotations, the description carries the full behavioral burden and discloses the fixed universe, SEC EDGAR source, classification logic, severity grading, and payment mechanism. It omits rate limits and error/failure behavior, but for an intel lookup tool this is substantial disclosure.

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 long but every sentence carries relevant information: purpose, universe, source, classification, filters, and payment. It front-loads the primary purpose and then details operational context, though a few clauses could be tightened.

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 tool is complex and has no output schema, so the description should explain return structure. It covers data provenance and classification but not the actual response shape, pagination, or error cases. Adequate for a basic call but not fully 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?

Schema coverage is 100%, but the description adds meaningful semantics beyond the schema: it explains that ticker can scan outside the default watchlist and that pillar filters by E, S, or G. This goes beyond the schema's generic 'Filter to one company'.

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?

Clearly identifies the resource as company-attributed ESG material-event intel from SEC filings and enumerates event types. It distinguishes itself from sibling tools like hsh-esg-news by specifying 8-K/SD sources and event-to-pillar mapping.

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?

Provides clear context on when to use it: to scan the fixed 35-name watchlist or pass a ticker to reach outside it. It does not explicitly name alternative tools or give when-not-to-use rules, but the context is strong enough to guide selection.

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