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

With no annotations, the description must disclose behavioral traits but doesn't. It doesn't mention return format, pagination, sorting criteria, authentication requirements, or any side effects. 'Search' implies read-only, but that's an inference, not a stated guarantee.

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 a single, efficiently worded sentence that immediately communicates the core purpose. No filler or redundant phrasing.

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?

The tool is simple, but the absence of annotations, output schema, and parameter documentation leaves significant gaps. The description fails to convey response structure, result ordering, or how 'top' is determined, making it under-specified for reliable agent invocation.

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%, so the description must compensate. It partially does by linking 'by username' to the query parameter and 'browse top' to omitting query. However, it never explicitly names the parameters or explains the limit parameter, leaving the agent to infer from names alone.

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's function: 'Search for builders by username or browse top builders.' It specifies the resource (builders) and the two modes of operation, distinguishing it from sibling tools like search_listings which target a different entity.

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 implies usage context (search vs browse) but gives no explicit when-to-use guidance or exclusions. It doesn't state when to prefer this over alternatives, nor does it explain parameter-dependent behavior. The two modes are mentioned but not tied directly to parameters.

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