endorse

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

With no annotations, the description carries full burden but only explains the tool's role in promotions. Lacks disclosure of side effects, reversibility, permissions, or constraints beyond the promotion context.

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 with no waste; purpose is front-loaded. Every word earns its place, efficiently conveying the tool's unique value.

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?

While output schema exists so return values are covered, the description misses parameter semantics and behavioral details. Adequate but incomplete for a tool with no annotations.

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 description coverage is 0% and the description provides no explanation of 'item_id' or 'note' parameters. Fails to add meaning beyond the schema, leaving agents uninformed about required inputs.

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?

Clearly states 'vouch for an item' as the action, specifying it as the strong trust signal. Distinguishes from sibling tools like 'promote' and 'review_promotions' by explaining its role in promotion workflows.

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?

Provides explicit context on when endorsement is needed (required for team->org promotion, fast-tracks local->team). While it doesn't enumerate when not to use, the promotion flow guidance effectively signals appropriate usage.

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