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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only nature is covered. The description adds the behavioral detail that it works for both users and organizations, which is not in the annotations. No side effects or auth requirements are mentioned, but given the annotations and tool simplicity, this is sufficient.

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 short sentences that front-load the core purpose. The second sentence is somewhat redundant but not wordy. The structure is efficient and clear, though it could be tightened further.

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?

The tool is simple with one parameter and no output schema. The description mentions the scope (user or organization) and establishes it as a profile getter. It does not specify response fields, but for a profile getter this is often implicit. The annotations cover safety, making the description adequate for correct invocation.

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% and the schema already describes the handle parameter, including the leading @ detail. The description's phrase 'Accepts a username' adds no new meaning beyond the schema. Since the schema fully documents the parameter, the baseline score of 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?

The description states a specific verb and resource: 'Get a GitHub profile' for a user or organization. It clearly differentiates from sibling tools by naming the GitHub platform and the profile resource, distinguishing it from activity lists, contributions, and repositories 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?

Usage is implied: when you need the basic profile of a GitHub user or org. However, it does not explicitly mention alternatives like github_profile_repositories_list or github_profile_contributions_get, so there is no when-not-to-use guidance. The sibling list suggests this is the base profile getter, but the description alone does not clarify when to prefer it over related tools.

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