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

Annotations already declare this a safe, idempotent read, so the bar is lower, yet the description still adds real behavioral context: results are limited to ID-checked, bookable creators, and returns carry hourly rates in ZAR plus a profile URL to book. It omits pagination/default-limit behavior, which is the only notable gap.

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?

Three tight sentences, front-loaded with what the tool finds, then filters, then return values. No filler or repetition of the title.

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 description helpfully explains the return shape (hourly rates in ZAR, profile URL). It is nearly complete for a simple search tool, with the only shortfall being undocumented query and limit semantics.

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 explains category (slug from list_categories or a specialisation like Photography) and city, but says nothing about the query or limit parameters, leaving half the inputs undocumented.

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?

States a specific verb+resource ('Search ... creators') with scope qualifiers ('ID-checked', 'open for bookings') that distinguish it from siblings like search_gear and get_creator. An agent can tell it finds creators rather than gear or a single profile without opening a schema.

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?

Gives clear context — browse/search creators who are bookable — and cross-references list_categories as the source for valid category slugs, which is genuinely actionable. It does not explicitly exclude alternatives (e.g. use get_creator for a known creator), so it falls short of a full when/when-not statement.

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