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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns behavioral signals (project age, commit frequency, contributor community, release cadence, social proof) and restricts to public repositories, but it does not mention edge cases like invalid/private repos or whether data is cached. This meets the baseline but lacks deeper behavioral disclosure.

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 compact and front-loaded, using three sentences to cover purpose, use cases, and examples. Each sentence adds value; the 'harder to fake' clause provides useful conceptual context without fluff.

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 single-parameter lookup with no output schema, the description gives sufficient context: what it does, what it returns, use cases, and example inputs. It omits error-handling or rate-limit details, but for the core decision and invocation scenario it is complete enough.

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 input schema already describes the 'repo' parameter with format and examples, and schema coverage is 100%. The description repeats example formats, reinforcing syntax but adding little new parameter-level meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the specific verb phrase 'Get a behavioral commitment profile' and clearly identifies the resource as 'any public GitHub repository', making the tool's purpose unambiguous. It distinguishes from sibling package lookups and from audit_github_repo by framing the output as a commitment profile rather than an audit.

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 'Useful for' list provides concrete scenarios (vetting open-source dependencies, evaluating AI tools/frameworks, assessing vendor reliability, due diligence) that tell an agent when to choose this tool. It does not explicitly name alternatives or exclude cases, but the context is clear enough to guide selection.

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