ctf_send

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

No annotations exist, so description must provide behavioral details. It mentions hex_mode behavior and return value (bytes sent), but omits side effects, state changes, or error handling. Minimal transparency.

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?

Description is concise with structured Args/Returns format. Every sentence adds value, though a brief usage hint would improve it further.

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?

Tool is simple with 2 params; description explains input and return. However, lacks behavioral context (e.g., is send blocking? what happens on failure?) and usage guidelines, which are needed given the complex CTF context.

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?

Schema coverage is 0%, so description fully compensates by explaining 'data' is the data to send and 'hex_mode' controls hex interpretation. Adds essential context beyond the schema's type-only definitions.

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 action ('向 CTF 程序发送数据' - send data to CTF program) and distinguishes from sibling 'ctf_sendline' which sends with line termination. The verb+resource pattern is specific.

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 guidance on when to use this tool vs alternatives like ctf_sendline or when to set hex_mode. The description only defines parameters without usage context.

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