Send a message to my parent

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

No annotations are present, so the description carries the burden. It discloses the parent-resolution mechanism, environment variable requirement, override parameter, and error condition. It doesn't cover delivery semantics or return value, but for a simple send operation this is substantial.

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?

Two sentences, front-loaded with the main purpose, and the rest specifies constraints; no filler or redundant repetition.

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?

For a 2-param tool with no annotations/output schema, the description covers purpose, parent resolution, required environment variable, defaults, and error handling. Remaining gaps (return value, delivery) are minor given the tool's simplicity.

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 covers only `from` fully; `body` lacks description. The description clarifies `body` as the message content and `from` as an override/default tie-in, adding value beyond the schema.

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 a specific action—'Message this pane's org parent'—and differentiates from generic send_message by specifying resolution via meta.parent and requiring a pane context. The scope and resource are clear.

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?

It identifies the use case (inside a pane with a parent) and prerequisites (HYPERPANES_PANE_ID or explicit from), and notes the error if no parent exists. It doesn't explicitly name alternative tools, but the context is sufficient to infer when this is appropriate.

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