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

Annotations already signal read-only, open-world false, idempotent, and non-destructive behavior. The description goes beyond this by disclosing specific behaviors: newest-first ordering, each item carrying a doc_id, capped lists marked as truncated, and a strict factual-data scope with no recommendations or targets. This is exactly the kind of contextual detail agents need to interpret results correctly.

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 concise and front-loaded, leading with the resource and document types before adding the truncation warning and factual scope note. Every part contributes useful information without fluff. The brief listing of content types justifies the term 'documents' and helps agents gauge relevance quickly.

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 there is no output schema, the description covers the essential return semantics: newest-first order, doc_id presence, and truncation behavior. It also clarifies the data scope, which is important for agents deciding whether this tool answers a user's request. It could be even more complete by describing pagination or the full set of fields returned, but for a simple read-only list it is largely sufficient.

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 schema already documents the company and doc_type parameters, including the enum values. The description adds a few examples that align with the enum but does not provide extra meaning about how the params behave or interact. A baseline 3 is appropriate because the description neither compensates nor needs to compensate 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 clearly identifies the resource as the documents MarketPing holds for a companyhare and provides concrete examples of the document types included. It also specifies ordering (newest first) and that each item has a doc_id, giving a precise operational picture. It does not explicitly differentiate this from search_filings or doc_contents, but the scope is much clearer than a generic statement.

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?

Description implies usage through its listing of document types and the caveat about truncated lists, which tells agents not to treat a truncated result as exhaustive. However, it does not explicitly state when to prefer this over search_filings or doc_contents, nor does it mention any exclusions. The factual-data clarification is a useful boundary but not a full routing guideline.

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