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

The description adds behavioral context beyond annotations: it discloses the 25-credit cost, the comprehensive nature (combining SEC, market, and exchange data), and the fact it runs multiple compliance checks. This enriches the readOnlyHint annotation without contradiction.

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 two sentences front-loaded with the core purpose, followed by details on what it covers and a cost note. Every sentence adds value with no redundancy.

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 presence of an output schema (so return values are documented elsewhere) and 100% schema coverage for the single parameter, the description is complete. It explains what the tool does, its scope, and cost, providing sufficient context for an AI agent.

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 input schema has 100% coverage with one parameter 'ticker' described as 'Stock ticker symbol.' The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the tool's purpose: 'Get full compliance rules evaluation for a company.' It specifies what it runs (Nasdaq/NYSE deficiency detection, bid price tracking, delinquent filing detection) and what it combines (SEC filing data, market data, exchange rules), making it distinct from siblings like get_insider_transactions or get_filing_document.

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 implies usage as the most thorough compliance check, with a cost of 25 credits. It provides context about the scope but does not explicitly state when to use vs. alternatives or when not to use it. A brief mention of when to prefer this over lighter tools would improve it.

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