Inspect Source, License, and Integrity

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

With no annotations provided, the description carries the behavioral disclosure burden. The verbs 'Get' and 'Inspect' imply a read-only operation, and the listed content areas indicate what is checked or retrieved. However, it does not explicitly state read-only behavior, access requirements, or whether any integrity check involves side effects, leaving some ambiguity for a zero-annotation tool.

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 a single sentence that front-loads the main purpose ('Get source inventory') and then enumerates the specific facets, which is efficient and easy to parse. It is slightly list-like, but each element adds distinct meaning and no filler is present.

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?

Although there is no output schema or annotations, the tool is low-complexity with no parameters. The description covers the full scope of what is returned: provenance, license terms, adaptation notes, limitations, and integrity. This is sufficient for an agent to know what to expect, even though the exact return structure is not specified.

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?

This tool has zero parameters, so the input schema is fully covered and there is nothing for the description to add about parameter semantics. The description appropriately focuses on output content. Per the rubric, a zero-parameter tool receives a baseline of 4.

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 states a specific verb ('Get') and a clear resource ('source inventory, provenance, license conditions, adaptation notes, limitations, and snapshot integrity'), which clearly indicates it is an inspection/retrieval tool for source-related metadata. It does not explicitly contrast with sibling tools like get_entry or list_entries, but the resource focus is distinct enough to avoid confusion.

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?

No guidance is given on when to use this tool versus alternatives. The description simply enumerates what it returns, leaving the agent to infer from the name and content that it is appropriate when source/license information is needed. There is no mention of exclusions or preferred sibling tools.

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