응급 상태 조회

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

Annotations already mark it read-only and idempotent. Description adds conditional behavior (bed info only if active session) and return fields. No contradictions, but edge cases not covered.

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?

Well-structured with main purpose first, conditional behavior, then args/returns in a list. Concise, slightly verbose in the returns section but still efficient.

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 one optional parameter, no output schema, the description covers purpose, parameter behavior, and return values. Lacks error handling info, but rest is sufficient.

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?

Single parameter session_id is described in both schema and description identically. Schema coverage is 100% so baseline 3 applies; description adds no new semantics beyond restating.

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 it queries emergency mode status and optionally retrieves real-time bed info. It distinguishes from siblings by using specific verb(조회) and resource(응급 모드 상태).

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?

Parameter usage is explained (session_id optional, defaults to latest). No explicit guidance on when to use this tool vs. siblings or when not to use it. Adequate but not explicit.

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