artist_completeness_score

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

With no annotations provided, the description carries the full burden and does disclose the key safety trait ('Read-only') plus the operational cap ('capped at 25 artists'). However, it is silent on the multi-request cost structure implied by dry_run and scan_cap, and on pagination/failure behavior — meaningful gaps for a tool that can issue up to 25 chained requests.

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 sentences, roughly 24 words, with the use case front-loaded and zero filler. Every clause earns its place: scenario, mechanism, output metric, safety trait, and cap.

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?

The core return concept (0–100% completeness score) is stated, which partially compensates for the absent output schema. But for a 5-param, multi-step tool with no annotations, the description leaves the result structure (per-artist breakdown vs aggregate), response_format semantics, and cost profile undescribed. Adequate for basic invocation, incomplete for confident use.

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 description coverage is 100%, and each parameter already carries a clear description (defaults, max, enum options, cost hints). The tool description only restates 'top N' and the 25 cap that top_n's schema entry already provides, so it adds no meaning beyond the schema — meeting the baseline for high coverage.

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 names a specific verb-resource pair ('fetch each artist's top tracks and score...') and defines the output metric (0–100% of saved top tracks). It also states the scope ceiling ('capped at 25 artists'), making the tool's function unambiguous even among many sibling 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 opening 'For your top N saved-track artists' implies the scenario, but the description never states when to prefer this over the many overlapping siblings (e.g., artist_complete_check, artist_top_vs_saved, artist_collection_gaps, library_coverage_report) nor gives exclusions. Usage is inferable, not explicit.

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