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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. It adds useful behavioral context: the source is the GitHub public API, there is a $0.02 USDC cost per call, and the returned fields include stars, forks, contributors, and language breakdown.

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 description is organized and front-loaded with usage context, followed by return fields, an example, source, and pricing. It is slightly wordy in the example's interpretive phrase 'strong community signal supporting enterprise adoption thesis,' but every sentence otherwise earns its place.

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 compensates by naming returned metrics and providing an illustrative example. It covers source and cost as well. It could be more complete by specifying the exact output structure and behavior for missing or unresolvable organizations, but it is adequate for a simple one-parameter read-only tool.

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 0% and the parameter 'org_or_company' has no schema description. The tool description implies the parameter is a company or organization name and gives HashiCorp as an example, but it does not explicitly state whether a GitHub org slug or a legal company name is expected, leaving some ambiguity.

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 names a specific verb and resource: assessing a vendor's open-source presence, developer community strength, and GitHub footprint before due diligence. It returns organization profile and top repository stats, which clearly distinguishes it from generic company-intelligence siblings.

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 opens with explicit 'Use when...' triggers covering three concrete scenarios. It does not name alternatives or give exclusion conditions, but it provides clear context for when the tool is appropriate.

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