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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so "never changes a pick" largely restates what is structured. It does add a small domain hint that picks are a separate concept unaffected by this tool. Return shape and result volume are not described, though the read-only profile is covered by 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?

Two short sentences with no padding, and the scope claim comes first. However, the compression is so aggressive that key terms ("Sourced", "jtbdIds", "pick") are undefined, so brevity costs comprehension rather than buying it.

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 two-parameter read tool with no output schema, the description is minimally sufficient to attempt a call. It omits the return shape and the meaning of the free/kind categories, which an agent would need to interpret results. Annotations cover the safety profile, so the remaining gap is moderate rather than severe.

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 100% and both parameters (jtbd, kind) carry schema descriptions, so the schema handles the semantics. The description adds nothing beyond the schema about the jtbd id format or what values "kind" accepts, and notably neither parameter is required despite the lookup seeming to need a jtbd.

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 implies a filtered lookup of $0/OSS resources matched by jtbdIds, but the verb is never stated and the wording is dense jargon ("Sourced $0 / OSS rows", "jtbdIds"). Compared with siblings like search, kit, and stack, nothing distinguishes when this narrow lookup is the right one.

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 statement of when to use this versus search, bundle, stack, or kit, and no prerequisite or exclusion information. The only guidance-like sentence, "Free never changes a pick," is a side-effect claim rather than a usage rule. An agent must infer the scenario entirely.

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