crompton_album_liner_notes

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

No annotations are provided, so the description carries full burden. It describes what the output contains (per-track counts, totals, pointers) and the nature of content (scene-setting). It does not mention side effects or errors, but for a read-only fetch with no parameters, this is adequate. Lacks details on response format but is still clear.

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 concise sentences. The first states functionality and output; the second gives usage context and content rules. No filler, front-loaded with the most critical information. Every sentence adds value.

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?

Given zero parameters and no output schema, the description is complete: it explains what data is returned, when to use the tool, and the nature of the content. The sibling list provides further context without needing explicit listing. Nothing essential is missing for correct invocation.

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?

There are no parameters, and the input schema is empty (100% coverage). Baseline for 0 parameters is 4. The description adds no parameter information because none are needed, which is appropriate.

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 states it fetches album-wide liner notes with per-track word counts, totals, and pointers. It explicitly distinguishes from the sibling tool crompton_liner_notes by framing as a bulk alternative ('instead of 13'). The verb 'fetch' and resource 'album-wide liner notes' are specific and unambiguous.

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?

Provides explicit usage guidance: 'Use for prompt-stuffing the atmospheric layer of the album in one call instead of 13.' It also clarifies content rules ('scene-setting, not story-canon') and references the sibling for individual notes. This effectively tells the agent when and why to choose this tool.

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