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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond the purpose restatement: it does not disclose the return shape, rate-limit or auth behavior for an open-world call, or what happens when target_user_name is omitted despite the schema marking it optional.

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 short sentence with no filler, and the core intent is front-loaded. The compactness comes at the cost of the ambiguous slash construction, but there is no wasted wording.

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?

There is no output schema, so the description carries the burden of telling the agent what a 'check' returns, and it does not. Combined with the undirected 'follows / is followed by' phrasing and the undocumented effect of omitting target_user_name, an agent cannot confidently interpret or invoke this tool for a two-direction relationship query.

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 parameters are already documented and the baseline is 3. The description names both parameters in a relational context (who follows whom), which is marginally useful, but it does not clarify the optionality of target_user_name or the direction semantics that the schema also leaves unstated.

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 verb 'check' and the resource 'follow relationship' are stated, so the general intent is identifiable. However, the phrasing 'follows / is followed by' leaves the direction ambiguous: an agent cannot tell whether the tool checks one direction, both, or returns separate booleans for each. The sibling names (get_list_followers, get_community_members) are not referenced, so nothing distinguishes this from broader follower-listing tools.

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 when-to-use guidance, no exclusion of alternatives, and no stated prerequisites. An agent has to guess whether this is the right tool versus get_list_followers or check_job_status-style status checks. The only implied usage comes from the name itself.

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