black_souls_get_scene_detail

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

Annotations already provide read-only and idempotent behavior. The description adds minimal additional behavioral context beyond stating it reads 'deeper state', which is consistent with annotations. No contradiction, but little extra value.

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 very short (one clause), no redundant information. It is front-loaded and efficient, though slightly vague. Could be improved by specifying what 'deeper state' entails.

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 no parameters, rich annotations, and the presence of an output schema (not shown), the description adequately sets expectations for a read-only tool. It mentions the three relevant scene types (map, battle, menu). The term 'deeper' suggests detail not captured in simpler state tools.

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 tool has zero parameters and schema coverage is 100%, so the description does not need to clarify parameters. However, it adds semantic value by specifying the scope (active scene), which is useful context for the agent.

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 verb 'Read' and the resource 'deeper state for the active map, battle, or menu scene'. It distinguishes from sibling tools like get_state or get_map by focusing on 'deeper state' and specific scene types, though the exact meaning of 'deeper' remains somewhat vague.

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 explicit guidelines on when to use this tool versus alternatives. The description implies it is for obtaining detailed state of the current scene, but it does not contrast with related tools like black_souls_get_state or black_souls_get_map, leaving the agent to infer the appropriate context.

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