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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context: the data originates from the latest DART periodic report (implying refresh cadence tied to filing dates rather than real time) and that an original-source link is included, which matters for verification.

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?

One front-loaded sentence with a colon-delimited list; every item earns its place because there is no output schema to describe return contents. Slightly dense enumeration, but no filler or 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?

With no output schema, the description must carry return-value meaning, and the enumerated sections plus the source-link note do that well for a single-parameter read tool. Minor gaps remain: output language, whether the result is a condensed summary versus full report text, and behavior for invalid or non-covered codes.

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 single parameter already carries an example (005930) plus the search_stocks fallback, so the baseline is 3. The description adds nothing further about the symbol argument, which is acceptable given the schema does the work.

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 names the exact resource (a standardized company profile derived from the latest DART periodic report) and enumerates the concrete sections returned: business description, segment revenue mix, industry position, major contracts, R&D, MD&A, and risk factors. That content list distinguishes it from siblings like get_news_summary or get_value_chain_position without needing to name them.

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?

There is no when-to-use guidance, no exclusions, and no pointer to alternatives in the description itself. The useful routing hint ('if you don't know the code, use search_stocks first') lives in the input schema, not the description, so the prose contributes nothing about tool selection.

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