tips

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

Explains core retrieval and ranking behavior (hybrid search with query; votes/recency otherwise). However, with no annotations, it omits return shape, side effects, and access requirements.

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 dense sentences, front-loaded with the core action and stripped of filler.

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?

With low schema coverage and no output schema, a read/list tool with six adjustable parameters needs more guidance about parameters and result shape. The description conveys overall ranking/query behavior but leaves tag, kind, scope, and output semantics unspecified.

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?

Only binding_token is documented in the schema and the description covers query behavior. Kind, tags, scope, max_results, and include_superseded are otherwise undocumented, and the description doesn't compensate for most of them.

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 identifies the tool as reading practical tips, with a specific retrieval behavior. It is distinct from nearby write/moderation tools like moderate_tip and tip_useful, though it doesn't explicitly state those exclusions.

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 clear guidance on what happens with vs. without a query, but does not say when to prefer this over sibling tools or when not to use it.

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