エンティティ一覧

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

Description confirms a read-only operation consistent with readOnlyHint annotation. It discloses that the response includes sceneGeneration, indicating a snapshot. No behavioral contradictions. While not detailing performance or edge cases, it adds context beyond annotations.

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, front-loaded with the core purpose. Every word serves a function. No fluff or redundancy.

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 presence of an output schema and full parameter descriptions, the description sufficiently covers purpose, behavior, and filters. A minor gap is lack of performance notes, but overall it's complete for a list tool.

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?

Input schema has 100% description coverage. The description reiterates parameter meanings (verbose adds componentTypes, name_prefix filters, component_type filters). It adds no new information beyond the schema, so baseline 3 is appropriate.

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 the tool returns a list of entities from the current scene with entityId and name. It mentions optional verbose for componentTypes and filtering options. This distinguishes it from siblings like dx12_get_entity or dx12_query_entities.

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 implies usage for listing entities in the current scene but does not explicitly contrast with alternatives like dx12_query_entities or provide when-not-to-use guidance. No exclusions or alternative tools are mentioned, so usage guidance is moderate.

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