get_company_info

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 clearly indicates a read-only retrieval (via 'Get') and specifies the output fields, which adds transparency. However, it does not address potential error behavior (e.g., invalid or missing corp_code) or any rate limits, leaving some behavioral ambiguity.

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 with no wasted words. It front-loads the primary action and resource, then lists the returned fields, and finally the key requirement. This is appropriately sized and structured for quick agent comprehension.

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 a single-parameter tool with no output schema, the description is fairly complete: it enumerates the return fields and the required input. It could mention what happens on lookup failure or note the regulatory context of DART, but these are minor gaps given the tool's simplicity.

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 only specifies the type and pattern for corp_code, with no description. The description compensates by explaining that this is the DART corporation code and that it must be 8 digits, adding semantic meaning beyond the raw schema. It also implicitly ties the parameter to the company profile look-up purpose.

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 uses a specific verb and resource ('Get company profile from DART') and enumerates the exact data fields returned (name, CEO, registration numbers, etc.). This clearly distinguishes it from siblings like search_disclosures and get_financial_summary, which serve different purposes.

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 states the prerequisite ('Requires DART corp_code (8-digit)'), which clearly indicates when to use this tool (when you have a corp_code). However, it does not explicitly mention when not to use it or provide alternatives from the sibling list, making the usage guidance implicit rather than explicit.

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