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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the data comes from the GitHub public API and gives an example output, but it does not disclose potential rate limits, data freshness limitations, or behavior for missing organizations. This is moderate added value beyond annotations.

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 three sentences, front-loaded with usage guidance, then returns, then an illustrative example. Every sentence earns its place, and there is no redundancy or padding.

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 tool with one parameter and no output schema, the description adequately explains what the tool returns ('organization profile and top repository stats with stars, forks, contributors, language breakdown') and provides a concrete example. It lacks edge-case handling or return-format details, but these are not critical given the simplicity and the presence of annotations.

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?

The schema has one parameter, org_or_company, with 0% description coverage. The description implies the input is a company or organization name through the HashiCorp example and the phrase 'company GitHub footprint,' but it never explicitly states that org_or_company should be the company name. This partially compensates for the missing schema description, justifying a baseline score.

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 clearly states the tool's function with specific verbs and resources: 'Returns organization profile and top repository stats — stars, forks, contributors, and language breakdown.' It also separates itself from sibling tools by focusing on GitHub ecosystem intelligence, distinct from broader vendor or market intelligence 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?

The description opens with explicit usage guidance: 'Use when assessing a technology vendor open-source presence, evaluating developer community strength, or researching a company GitHub footprint before a technical due diligence.' It provides clear context but does not mention when not to use it or name alternatives, so it stops short of a 5.

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