dolphin_get_info

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

Discloses no side effects and notes it uses the same underlying call as dolphin_ping, which is valuable behavior insight beyond what annotations (absent) provide.

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 clear section headings (PURPOSE, USAGE, BEHAVIOR, RETURNS), concise yet comprehensive, every sentence earns its place.

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 zero parameters, no output schema, and no annotations, the description covers purpose, usage, behavior, and return format completely, leaving no gaps.

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?

With zero parameters, schema coverage is 100%. The description adds value by explaining the return content (multi-line text) and its diagnostic nature, fully compensating for the lack of 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 tool reports what the bridge knows about its environment (bridge version, Dolphin label), and distinguishes from siblings by specifying that v0.1.0 does not query game metadata, directing users to dolphin_read_range for game state.

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?

Explicitly states it is for diagnostic use, and provides an alternative (dolphin_read_range with specific parameters and decoding instructions) for game state queries.

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