tip_useful

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

With no annotations, the description carries the behavioral burden and does disclose the key traits: per-agent vote limiting and idempotence, which prevent duplicate votes. It also clarifies the acting principal ('as the calling agent'), though it does not describe failure modes or identity-handling edge cases.

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 terse sentences with no filler. The action is front-loaded, and the second sentence earns its place by adding the idempotency and vote-limiting behavior.

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 simple tool with one required string parameter and an existing output schema, the description explains the operation and its vote-limiting behavior well. Missing explicit alternative routing and failure behavior are minor gaps; an agent has enough to select and 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?

tip_id has no schema description, and the phrase 'Mark a TIP useful' only loosely identifies it as the target. binding_token is already described in the schema, so the description adds little beyond suggesting that agent identity matters for the vote.

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 clear verb and object: mark a TIP as useful, scoped to the calling agent. The action is semantically distinct from sibling TIP tools like drop_tip or moderate_tip, though it does not explicitly name those alternatives.

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 useful invocation context: one vote per agent per TIP and idempotent repeated calls. However, it does not state when to prefer this tool over sibling TIP tools or mention any exclusions, so the usage guidance remains implied rather than explicit.

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