pine_get_info

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

Describes behavior in detail: no side effects, pure read, issues five opcodes in parallel, returns '(unavailable)' for failed fields, propagates error on connection failure. Annotations absent so description carries full burden.

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 PURPOSE, USAGE, BEHAVIOR, RETURNS sections. Every sentence adds value, no fluff. Efficient despite length.

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?

Complete for a no-parameter tool without output schema. Explains return format (multi-line text with fields), parallel opcode behavior, error handling, and field failure behavior.

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 zero parameters, baseline is 4. Description adds meaning about returned fields but no parameter details needed.

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 gets loaded game metadata and run state, with specific fields listed: title, serial code, disc CRC, game version. It distinguishes from siblings like pine_get_status which only gets run 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 instructs to call after pine_ping, warns against blind memory poking, and directs to pine_get_status for just run state. Provides contextual usage: serial identifies region, CRC identifies revision.

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