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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description does add cost transparency ('Repeated requests may purchase data again'), which is genuinely valuable beyond annotations. However, the cost statements conflict internally ('at least 10 Nexscope credits' vs '1 credit per request'), which undermines the transparency it attempts to add.

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?

The core sentence is well front-loaded, but the text is bloated with duplicated content ('Get public repositories for a GitHub user. Supports pagination...') and pasted pricing boilerplate ('GitHub Repositories API View Pricing', 'Actual supplier units are reported per request. Examples are not guaranteed prices.'). Roughly half the text does not help an agent decide or call correctly.

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 usefully enumerates the returned fields, and it flags that at least one identifier must be supplied despite an empty required list. Six optional params are all schema-documented. Only the missing sibling differentiation and the muddled pricing detail keep it short of full completeness.

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% with enums on type, sort, and direction, so the schema already documents every parameter's meaning and defaults. The description's only added semantic is that username, handle, and url are interchangeable identifiers, which is mildly useful but largely redundant with the 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?

The description opens with a specific verb+resource: 'Retrieves a user's public repositories,' and enumerates the returned metadata (language, stars, forks, topics, license, visibility, default branch, timestamps). It distinguishes implicitly from the single-repo sibling (social_github_repository) by emphasizing 'a user's ... repositories,' but never explicitly contrasts with social_github_trending_repositories or social_github_user.

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 line 'Pass username, handle, or url' gives useful input-selection guidance, and pagination/sort options are noted. But there is no when-to-use guidance versus alternatives, no exclusions, and no statement of prerequisites or error conditions.

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