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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so 'read-only: returns public data and changes nothing' largely restates what is already structured. The one genuinely additive fact is the cost signal, 'Costs 1 credit per request', which is behavior an agent cannot get from the schema or annotations. Return shape and result-set limits are left unexplained, though the schema's count cap of 10 partly covers that.

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 clauses, front-loaded with the resource identification, with no filler or preamble. The read-only sentence partly duplicates the annotations, which is minor waste but not enough to undermine the efficient framing.

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 12 parameters, three required fields, nested range filters, and no output schema, the definition is thinner than the tool's complexity warrants. The agent is not told what a result record looks like or that paging is handled through the cursor field, forcing it to reconstruct that from the schema alone.

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 every parameter, including the nested gt/gte/lt/lte range objects and the cursor, carries its own documentation, so the schema does the heavy lifting. The description adds no semantic detail beyond it and does not mention the required sort/order/count triplet or pagination via cursor, so the baseline 3 applies.

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 uses a specific verb ('Search') plus a precise resource ('GitHub users and organizations'), which cleanly separates it from siblings like github_search_repositories, github_search_code, and github_search_issues. It stops short of naming the closest lookup alternative, github_get_profile, so an agent must still infer which one applies to a known handle.

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 or when-not-to-use guidance and no named alternative. The description never says to prefer github_get_profile when a specific username is known, nor how this differs from x_search_users or reddit_search_users among the siblings.

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