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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context: 'blocks degrade independently' (partial data availability) and specifies data provenance ('from board-relationship', 'from executive-compensation'). It does not explicitly declare safety (read-only) or return format, but for a data-aggregation tool, the disclosed behavior goes beyond a bare description, warranting a high score.

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 packs a significant amount of information into two well-organized sentences. The first sentence lists the datasource contents with parentheses for clarity, and the second provides usage and exclusion guidance. No filler or redundancy; every clause earns its place.

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?

Given the tool's moderate complexity and lack of an output schema, the description covers the key content areas and usage context. It lists all data components, mentions 'blocks degrade independently', and points to an alternative for adjacent needs. It stops short of detailing the exact response envelope or error behaviors, but for a one-parameter retrieval tool, this is sufficient to set expectations.

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 schema has 100% coverage for the single 'ticker' parameter, so the baseline is 3. The description does not add extra meaning about ticker formats, case sensitivity, or examples. Since the schema itself sufficiently describes the parameter (required path parameter), the description earns the baseline but no more.

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 opens with a clear, specific verb-resource combination: 'One-call corporate-governance dossier'. It enumerates exact contents (board size, composition, interlocks, restatement record, auditor-change history, executive compensation) and explicitly differentiates from alternatives via the red-flag alternative reference. This unambiguously identifies the tool's purpose and scope.

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 description provides explicit usage guidance: 'Call it for any management-quality, board-oversight or comp question'. It also gives a direct alternative for a different use case: 'For graded forensic red flags use /api/v3/intel/accounting_flags'. This covers both when to use and when to avoid, exceeding baseline expectations.

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