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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail: it computes a signature, searches a live leaderboard, and returns specific comparative fields, including where the operator outperforms you and vice versa. No contradiction with annotations.

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 front-loaded with the core purpose and then compactly explains the process and return values. Every sentence contributes something except the final stylistic sentence, which is not harmful but adds little operational 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?

With no output schema, the explicit list of returned information is helpful. However, the description is incomplete for a 7-parameter tool: it does not clarify how to supply the 4 pillars, what the cache parameters mean, or how the optional parameters interact with defaults. It covers the primary use case but leaves too many operational details unresolved.

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 only 29%, so the description must compensate, but it merely says '4 pillars or a codename' without mapping '4 pillars' to the input parameter or explaining how the numeric input should encode them. The codename and limit are documented in the schema, but output, cache_read, and cache_write remain undefined in both schema and description. The lack of required parameters also creates ambiguity about whether pillars are optional or default to the current operator.

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 states a specific outcome—finds operators whose operating signature most resembles yours—and explains the mechanism: compute signature from 4 pillars or a codename and search the live leaderboard by signature distance. It clearly differentiates from siblings like get_leaderboard by describing the result as a network rather than a list.

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 when to use the tool—when you want similar operators and a comparative breakdown—but it never explicitly says when not to use it or which alternative to choose. There is no routing guidance such as 'use get_leaderboard for raw lists' or 'use operator_signature for just a signature.'

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