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

Annotations already establish readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond those annotations: each returned id is the request id for accept_follow_request, and the operation 'counts as browsing,' which hints at rate-limit or account-activity implications. It still omits pagination behavior, but the schema documents cursor and limit.

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 are front-loaded with the resource definition, followed by the cross-tool id usage and browsing note. There is little wasted text, though 'Counts as browsing' is terse to the point of being slightly cryptic.

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 simple read-only paginated list with annotations covering safety, the description supplies the core resource meaning, a key return-value usage, and a browsing caveat. Remaining gaps are minor: account_id is not explained and page-size behavior is left to the schema, but an agent has enough to call the tool correctly.

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 67%, with limit and cursor well documented but account_id undocumented. The description implies the account is the private Instagram account whose pending requests are listed, adding marginal meaning for the required parameter, but it does not explicitly explain account_id or add syntax beyond the schema.

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 description identifies a specific resource: people asking to follow a private Instagram account, which distinguishes pending follow requests from actual followers or following lists. The listing verb is implicit from the tool title rather than stated in the description, and no sibling is named explicitly, so it is clear but not maximally differentiated.

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?

The description implies a browsing/read use case through 'Counts as browsing' and explains that returned ids feed accept_follow_request, which gives some actionable context. However, it does not state when to use this tool instead of list_followers or list_following, nor does it mention prerequisites such as the account being private.

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