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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful context beyond that by flagging that the record is self-attested, not third-party audited, and that only git stats are independently inspectable—an important trust caveat for how the returned data should be interpreted.

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 dense but not bloated; every clause contributes either content or an important caveat. The parenthetical caveat interrupts the flow slightly, but the overall structure effectively front-loads the core resource and then lists its contents.

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 zero-parameter, read-only tool with no output schema, the description explains the nature of the record and enumerates its main fields, which is sufficient for a first call. It could be slightly richer on what 'verification endpoints' means or how the record is obtained, but nothing critical is missing.

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 tool has zero parameters, so the description cannot add parameter-level meaning. The schema coverage is trivially 100%, and the description rightly focuses on what the returned record contains rather than on nonexistent inputs.

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 identifies the resource as an 'AI-native provenance record' and names its concrete contents: live git stats, AI authorship percentage, founder credentials, patents, and verification endpoints. This is specific enough to distinguish it from the many other getter tools, none of which target provenance proof.

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 explicit guidance about when to call this tool versus alternatives, nor any mention of when not to use it. The purpose implies usage, but the description never states a use case or points to a sibling tool, so an agent gets no routing help.

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