ksei_investor_demographics

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

Without annotations, the description must fully disclose behavioral traits. It only states 'Get' (read operation) but omits details like data update frequency, range limitations, or response format. The minimal behavioral disclosure is insufficient for an agent to understand side effects or constraints.

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 sentence, which is concise, but it omits critical information. Like the 'Process' example in calibration, this is under-specification rather than effective conciseness. Every sentence should contribute, but here it sacrifices completeness.

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 has 2 parameters (one with enum), no output schema, no annotations, and 0% schema coverage, the description is grossly incomplete. It fails to specify input formats, return values, or any operational details needed for correct invocation.

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 has 0% description coverage, and the description adds no meaning to the two parameters. It does not explain the required format of 'month_year' (e.g., YYYY-MM) or the values of the 'dimension' enum (e.g., what 'income' ranges are). The agent cannot infer correct usage from this definition.

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 KSEI investor demographics by month and dimension. It uses a specific verb ('get') and resource ('demographics'), distinguishing it from sibling tools like ksei_sid_growth. A score of 5 would require explicit differentiation from siblings, which is implicitly achieved.

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 is provided on when to use this tool versus alternatives. The description lacks context about the proper scenarios for using demographics vs. other KSEI tools, such as ksei_sid_growth.

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