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

Annotations cover the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false) but say nothing about outcomes. The description adds material behavioral detail beyond them: tier-dependent handling (Pro accounts are checked and added immediately), a hard rate limit ('up to 5 a day'), and a pending-review path for everyone else. That is exactly the kind of context annotations cannot express.

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?

Two sentences, zero filler. The purpose statement is front-loaded, and the operational caveats (Pro vs. review, daily cap, confirm link first) follow in descending order of importance.

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 still tells the agent what happens after the call (added immediately or queued for review) and what to do beforehand. It leaves unstated what the tool returns on success, which is a minor gap for a two-parameter submission tool.

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 100%, so both url and note are already documented, and the description's mention of 'YouTube channel or X profile link' merely restates the url schema description. It adds no syntax, format, or constraint detail beyond the schema, so the baseline 3 is appropriate.

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 ('suggest') and resource ('a finance influencer ... to track'), plus the accepted identifier forms (YouTube channel or X profile link). An agent can tell this apart from read-oriented siblings like influencer, rank_influencers, and influencer_performance. It stops short of naming a sibling it should be preferred over, which is what would earn a 5.

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 a concrete prerequisite ('Confirm the link with the user before calling') and frames the call as a suggestion/submission rather than a lookup. It does not name alternatives or state when-not to call it (e.g. for an influencer already tracked), so it falls short of the explicit when/where-not/alternatives bar.

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