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

Annotations already declare readOnly/idempotent/non-destructive, so the trailing 'Read only' adds little. The description does add genuinely useful data semantics beyond annotations: follower count is present only when public, otherwise null, and must never be estimated. That is real guidance an agent cannot get from the structured fields.

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?

A single dense, front-loaded sentence that enumerates the payload fields before the trailing safety note. The final 'Read only' is redundant with the readOnlyHint annotation and could be dropped, but otherwise there is no waste.

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 responsibly lists the returned fields and the null-follower rule, which is the main thing an agent needs. The remaining gap is the provenance/format of searchId, which is left for the caller to infer.

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?

One param at 0% schema description coverage, so the description must carry the load. 'By one search' conveys that the id scopes to a single search, but it never states the parameter is a search UUID or where to obtain it (e.g., from soclo_creators_search). Partial compensation only.

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: returns the creators produced by one search, and enumerates what each record carries (profile link, source page, fit rationale, follower count). Clearly a read of a single search's results, distinguishable from sibling soclo_creators_search (which runs a search) by the word 'found', though it never names that sibling.

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?

'Creators found by one search' implies it is called after a search exists and applies to a single search, but there is no explicit when/when-not and no mention of soclo_creators_search or soclo_creators_searches as the source of the id. Usage is inferred, not stated.

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