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

Goes well past the annotations: discloses the account/list prerequisite, the error surfaced when setup is missing, and the read-back verification semantics (confirmed arrived, missing stayed unmarked and will be retried on the next send). That retry/non-idempotent behavior is exactly the kind of context an agent cannot infer from idempotentHint=false alone.

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?

Three short sentences, front-loaded with the action, then prerequisites, then result semantics. No filler, and every sentence carries distinct information.

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?

There is no output schema, yet the description explains what the caller learns from the result (confirmed vs missing) and the retry consequence of a missing item. Combined with the error condition, that is everything needed to invoke and interpret the call.

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 tool takes zero parameters, so the schema baseline of 4 applies and there is nothing additional to document. The description correctly adds no parameter noise.

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?

States a specific verb (Send), a specific resource (open Joiva shopping entries) and a specific destination (the user's connected Bring! app). It is clearly distinguishable from the sibling shopping tools such as joiva_list_shopping or joiva_add_shopping_item.

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 makes clear this is the push-to-external-app action and spells out the prerequisite state (linked Bring account plus a picked list), including what happens when that precondition is unmet. It does not name an alternative tool or an explicit 'don't use this when' case, so it stops short of a 5.

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