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

With no annotations, the description carries the full burden and does disclose the two most important behaviors: human moderation before listing and a deduplication rule against existing listings. What it omits is the outcome of a call (confirmation, rejection, async status) and any limits on repeated submissions.

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 short sentences, each earning its place: what to submit, what review happens, and what not to submit. The purpose is front-loaded ahead of the constraints.

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 three-parameter submission tool with no output schema and no annotations, the description covers purpose, inputs, moderation, and deduplication. Only the post-call result is left unspecified, which is a minor gap at this complexity.

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 coverage is 100%, so the baseline is 3; the description adds a bit of meaning by clarifying that the link may be either an x.ai/bot share link or an X post URL, matching the intent of the required 'link' field. It says nothing about 'name' or 'note', but those already have schema descriptions.

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 and resource ('Suggest a Grok Bot for Bot Shelf') with the two acceptable artifacts, which immediately separates it from the read-only siblings find_bots, get_bot, latest, and list_categories.

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 conditions for use, notably 'A person reviews every suggestion before it is listed' and 'Bots already listed are not resubmitted', which tells the agent submission is a moderated queue and that already-catalogued bots should not be resubmitted. It does not explicitly name a sibling to use instead when the bot is already listed (e.g., get_bot to check).

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