ksei_sid_growth

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

No annotations are provided, so the description bears full responsibility. It only says 'Get,' implying a read-only operation, but fails to disclose authentication requirements, rate limits, data freshness, or any side effects. The term 'official' adds minimal context.

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 a single, front-loaded sentence of 11 words with no redundancy. Every word adds value.

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 and minimal parameter guidance, the description fails to cover response format, error conditions, or constraints. For a tool with two required string parameters, more detail is needed for reliable use.

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 0%, meaning parameters have no descriptions in the schema. The description mentions 'by month and metric' but does not explain valid formats for month_year (e.g., 'YYYY-MM') or the allowed values for metric (e.g., 'investor_count', 'growth_rate'). This leaves significant ambiguity for correct invocation.

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 specifies 'Get official KSEI investor-count growth series by month and metric,' providing a clear verb (Get), resource (KSEI investor-count growth series), and dimensions (month, metric). It is distinct from sibling tools like idx_* (company info) and ksei_investor_demographics, but does not explicitly differentiate itself.

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?

No guidance on when to use this tool versus alternatives (e.g., bps_get_data for economic data, idx_company_announcements). The description only states what it does, not when it is appropriate or not.

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