lexicon_library_stats

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It hints at output (totals, incoming, tracks without genre) but does not mention whether the operation is read-only, destructive, requires authentication, or has any side effects or limitations. This is a significant gap.

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 with no unnecessary words, achieving conciseness. However, it is too brief and sacrifices informativeness. While front-loading the purpose, it fails to add crucial details.

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 the tool has one undocumented parameter, no output schema, and no annotations, the description is severely incomplete. It does not explain what 'library health' or 'incoming' means, nor does it describe the format of results. The tool likely returns complex data, but the description omits all context.

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 input schema has a single parameter 'sampleLimit' which is completely undocumented in the description. With 0% schema description coverage, the description should compensate but does not. The parameter's meaning, possible values, and effect are absent.

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 that the tool summarizes library health, enumerating specific outputs like totals, incoming, and tracks without a Genre tag. This distinguishes it from sibling tools like lexicon_list_tracks or lexicon_list_incoming, which serve different purposes.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or when not to use it. The implied usage is for obtaining a summary, but no explicit directives are given.

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