bardo_feedback

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

The description goes beyond annotations by detailing behavioral traits: one-way and stateless, no memory across calls, and that operator replies appear as ordinary notices. This adds critical context not present in the minimal annotations.

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 longer than necessary but each sentence adds value: purpose, statelessness advice, and reply mechanism. It is front-loaded with the main action. Minor redundancy could be trimmed, but overall it is effective.

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 no output schema and limited annotations, the description provides sufficient context for correct usage: purpose, behavior, parameter meanings (except session_token), and integration with notices. It covers the essential aspects for an agent to invoke the tool properly.

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 description explains the 'kind' parameter with its three allowed values and implies 'message' is the content. However, it does not mention 'session_token', which is undefined in the schema with 0% coverage. The description partially compensates for the missing schema descriptions but leaves one parameter unexplained.

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 sends feedback to Bardo's operator, listing specific kinds (suggestion, complaint, security). It uses a specific verb 'send' and resource 'feedback', differentiating from sibling tools like bardo_notices which handle replies.

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 explains when to use the tool (sending feedback) and provides explicit guidance on statelessness: say everything in one message as follow-up calls won't retain context. It also notes that replies arrive as bardo_notices, directing the agent to an alternative for receiving responses.

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