safetynet_how_to_help

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose a key safety trait ('This site never holds the money') and describes the process of sending value and recording transactions. However, it does not explain what the tool actually does (e.g., returns step-by-step instructions), any side effects, or the response format. This partial transparency warrants a 3.

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 two concise sentences that front-load the topic and provide a key safety note. There is no filler or redundant wording. It is appropriately sized for an instructional tool and structured efficiently.

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?

This is a simple tool with one parameter, but the description is incomplete. It does not explain what cardId is used for, what the tool returns (e.g., text instructions), or any prerequisites. Since there is no output schema, the description should clarify the output. The description focuses on the domain but not the tool's operational behavior, leaving significant gaps for an agent.

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 schema has one parameter, cardId, with no description, and schema description coverage is 0%. The description does not mention cardId at all, so it adds no meaning to the parameter. An agent would have no idea what to pass or why. The description completely fails to compensate for the missing schema documentation.

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's purpose: providing guidance on how to help someone on SafetyNet by sending value directly and recording the transaction. It distinguishes itself from other how-to tools by specifying the SafetyNet context, and from safetynet_cards which likely deals with card management. However, it doesn't explicitly state that it returns instructions or a guide, so the purpose is clear but not fully explicit.

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?

There is no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it, nor does it compare to sibling tools like safetynet_cards or other how-to tools. The description implies it is for understanding how to help, but lacks explicit usage context or exclusions.

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