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

Annotations are empty, so the description carries the full burden. It only states the search action and fails to disclose side effects, permissions, rate limits, or return behavior. There is no mention of whether the operation is read-only or if it invokes external services.

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 concise sentence that front-loads the core verb and resource, with no filler or redundant information. It earns its place and is easily scannable.

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 the enormous 43-parameter schema, no output schema, and empty annotations, the description is drastically incomplete. It provides no information about return values, input mapping, pagination, or edge cases, making reliable usage impossible without additional context.

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 has 43 parameters with only 33% description coverage, and the description adds no parameter details whatsoever. It does not indicate which parameters (e.g., query, audience) are relevant or how to use them, leaving agents unable to form valid inputs.

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 uses a specific verb 'Search' and identifies the resource 'creator catalog', explicitly stating it finds the best approved free, subscriber, or paid item for a user's situation. This clearly distinguishes it from sibling tools like wisely_creator_catalog_list and wisely_creator_catalog_fetch.

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 a use case—finding the best item for a user's situation—but provides no explicit alternatives or when-not-to-use guidance. It does not mention sibling tools or exclusion criteria, leaving the when-to-use entirely implicit.

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