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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it provides essentially none. It does not mention whether the operation is read-only, what results look like, whether there are limits, or any other behavioral trait. The phrase 'free text or code' only hints at input flexibility, not behavior.

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 extremely concise and front-loads the core idea without filler. It earns its place but is arguably too sparse to fully inform an agent, which is why it does not reach a 5.

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?

Given there is no output schema, no annotations, and a sibling set full of similar search/get pairs, the description is not complete enough. It fails to state what results surface_search returns, what 'Surface' represents, or how this search differs from sibling search tools.

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 schema provides no description for the single parameter 'q' (0% coverage), so the description's 'free text or code' adds some meaning by indicating the accepted query format. However, it lacks examples, constraints, or elaboration on what kinds of code or text are expected, so it only partially compensates for the missing schema documentation.

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 identifies a resource ('Surface') and indicates the search input type ('free text or code'), which is somewhat informative. However, it is a fragment rather than a clear statement of what the tool does, and it does not distinguish surface_search from surface_get or other sibling search tools beyond what the name already implies.

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?

There is no guidance on when to use this tool versus alternatives such as surface_get or the other search tools. No contexts, exclusions, or preferred use cases are provided, so an agent must infer usage entirely from the tool name.

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