console_send

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

Beyond the annotations, the description discloses useful behavior: the newline appending when newline=True and the tool error condition for invalid sessions. It aligns with destructiveHint and does not contradict annotations, though it does not elaborate on side effects beyond signaling a write operation.

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, front-loaded with the core action. Every sentence adds value: the first states the primary purpose, and the second covers important behavioral details without fluff.

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 the tool's simplicity, the existing annotations, and an output schema, the description is complete. It covers the write action, the newline behavior, and the key error condition, leaving no significant gaps for an agent to invoke the tool correctly.

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 0% schema description coverage, the description compensates by explaining the data payload, the newline flag's effect, and session validity. It does not give an explicit definition for the session property, but the open-session framing and error condition add enough meaning for an agent to infer its role.

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 states 'Write data to an open console session' with a specific verb and resource, making the tool's function immediately clear. It also distinguishes itself from siblings like console_read and console_close by focusing on the write operation.

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?

The description clearly indicates the tool must be used with an open session and that unknown, closed, or errored sessions are errors. It does not explicitly name alternatives or exclusions, but the sibling tools and the phrase 'open console session' imply the intended usage context well.

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