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

The description goes well beyond the readOnly/idempotent annotations by disclosing fan-out behavior across sources, soft-failure of the USPTO PatentsView API, and the meaning of empty sections via sources_used/sources_failed. It also states that private companies return an explicit resolved:false with notes, which is important behavioral context for an agent.

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 dense and front-loaded with purpose, and the extensive detail is justified by the lack of an output schema. However, it is one long block that partly repeats schema documentation, and it could be structured into shorter scannable segments without losing information.

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 multi-source complexity and absence of an output schema, the description is remarkably complete: it enumerates sources, return fields, failure semantics, fallback routes, and input resolution behavior. An agent has enough context to invoke it correctly and interpret results accurately.

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% and the input schema already explains that type accepts 'company' or 'ticker' and that value can be a ticker, zero-padded CIK, or company name. The description largely repeats this information rather than adding new parameter semantics, so the baseline 3 applies.

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 concrete query examples and defines the deliverable as a 'full cross-source profile of a US public company in ONE parallel call.' It clearly names the resource (company profile) and distinguishes the tool from single-pack SEC/XBRL/news lookups, so an agent can identify its intended job.

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?

It gives explicit when-to-use guidance: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also specifies acceptable input forms (ticker, CIK, company name) and notes that private companies return resolved:false rather than being treated as a failure.

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