get_company_profile

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the source (Open DART) but does not state whether authentication is required, how fresh the data is, whether it is read-only, or if there are rate limits or error conditions.

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 short and immediately states the tool's purpose, then follows with a clear parameter breakdown and a useful example. Every sentence earns its place without redundant detail.

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 simple one-parameter tool with an output schema, the invocation details are mostly sufficient. However, the description omits when to use this tool instead of get_company_profile_by_query, and does not mention any prerequisite like an Open DART API key, which is a notable gap given the sibling tools include check_dart_api_key.

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 provides only the parameter name and type with 0% coverage, but the description compensates well by explaining that corp_code is an eight-digit Open DART corporation code and giving a concrete example (Samsung Electronics is 00126380). This gives the agent enough context to supply the parameter correctly.

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 retrieves official company information from Open DART, with a specific verb and resource. However, it does not explicitly distinguish itself from the sibling get_company_profile_by_query, which likely serves a similar purpose via different lookup criteria.

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 no guidance on when to use this tool versus alternatives like search_company or get_company_profile_by_query. It only explains the required corp_code argument, with no mention of preferred scenarios or exclusions.

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