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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds non-obvious behavior: enrichments can degrade, and unavailable ones are reported in 'degraded' without failing SEC data, plus the conditional prerequisites for hiring. It omits pagination/size behavior but adds meaningful context beyond annotations.

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?

Four tight sentences, front-loaded with the primary purpose followed by enrichment conditions and routing. Slightly dense with in-group jargon ('board locator', 'degraded'), but every clause carries actionable content and nothing is redundant with the schema.

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 an 8-parameter, zero-required aggregation tool with an output schema, the description covers purpose, enrichment conditionality, and degradation behavior. What remains absent is how cik vs ticker precedence is resolved when both are supplied, a minor gap given an output schema already exists to explain results.

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%, so the baseline is 3, but the description goes further by explaining conditional parameter relationships: hiring requires ats and its board locator, which links ats to careers_slug/tenant/site/datacenter that the schema documents only in isolation. It clarifies enrich as an optional comma-list of market/news/hiring, which is genuine added meaning.

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?

States a concrete verb (summarize) and a well-scoped resource set (SEC profile, annual financial snapshot, recent filings, material events) keyed by cik or ticker. It also explicitly names the sibling it is not (sec_financials for multi-period statements), so an agent can route between them without opening schemas.

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?

Gives clear usage context and one explicit alternative routing rule ('Use sec_financials for multi-period statements'), plus a prerequisite for the hiring enrichment. It does not state when not to use the tool at all (e.g., pure filing-text needs belong to sec_filing_sections), so it falls just short of the full when/when-not bar.

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