選択

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

Discloses the state change (set selected) and side effect (Inspector display switches). Annotations confirm idempotency, aligning with the description. No contradictions.

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 concise sentences cover purpose, parameters, and return value without wasted words.

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?

For a simple selection tool with good annotations and schema coverage, the description fully addresses usage and behavior. Mentions return value {selected}, completing the picture.

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?

Adds significant meaning beyond schema: name is exact match and stable after Stop. Schema coverage is 100%, but description provides practical usage context for both parameters.

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 action (select) and resource (entity) with specific verb '選択する'. It distinguishes from sibling tools like dx12_find_entity or dx12_get_entity by focusing on selection state for Inspector display.

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?

The description specifies usage parameters: entity by id or name. It implies when to use (to select an entity for editor interaction) but does not explicitly exclude alternatives or provide when-not guidance.

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