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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so safety signalling is covered. The description adds nothing beyond that — not what state is written, whether the creator is excluded from future searches, or whether the action can be undone.

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?

One short front-loaded sentence with no filler, but it is under-specified rather than genuinely concise — there is room for another clause explaining the effect without bloat.

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?

For a destructive, open-world mutation with no output schema and an undocumented parameter, the description leaves an agent missing the effect of the call and how to obtain candidateId. It is far from sufficient to invoke confidently.

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% and the single required parameter candidateId is never mentioned in the description. With one destructive identifier parameter, the description should at least confirm it takes the creator/candidate id from a search or shortlist result.

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 phrase 'Mark a creator as not a fit' paraphrases the title 'Dismiss a creator' and adds a little semantic shading (a fit judgment, not e.g. a deletion). It never says which creator record is affected or what 'not a fit' changes in the system, and it doesn't distinguish this from neighbouring creator tools like soclo_creators_shortlist or soclo_creators_pitch_reject.

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 dismiss versus the available alternatives (shortlist, pitch/reject, remove). An agent has to guess whether this removes a creator from search results, from a shortlist, or flags them globally.

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