get_institution_staff_summary

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

No annotations present. Description discloses return of authorized vs actual categories and a specific field note, but lacks details on authentication, rate limits, or behavior with missing parameters. Some transparency but gaps remain.

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?

Two sentences with clear structure, front-loaded with key action. Second sentence adds value but could be more structured. No waste.

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 4 parameters and no output schema or annotations, description lacks parameter explanations, return format, and prerequisites. Usage examples help but incomplete for effective 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 has 0% description coverage for 4 parameters. Description does not explain org_code, query, year_from, or year_to. No parameter semantics added beyond schema titles.

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?

Description clearly states it summarizes institution staff by distinguishing authorized (정원) vs actual (현원) and gives query examples, differentiating it from sibling tools like get_institution_metrics or get_institution_profile.

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?

Describes when to use (queries about staff count) and provides guidance on interpreting headcount.estimated_total. No explicit exclusion of alternatives, but context is clear.

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