Classify hook

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

Annotations declare destructive/openWorld/non-idempotent, and the description corroborates and enriches: 'replace its stored hook analysis' discloses the destructive overwrite, requires a saved Anthropic key, and warns that title, transcript and comment context are sent to an external provider. Describes returned fields and the taxonomy-entry side effect.

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?

Three tight sentences, front-loaded with the action, followed by routing and the material behavioral caveats. Every sentence carries distinct information.

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?

No output schema exists, and the description fully compensates by naming the return values (hook, explanation, confidence, correction count) plus the taxonomy-entry side effect. Key requirement and external-data transmission are both covered, so an agent has everything needed to call it correctly.

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 the sole slug parameter is already documented with its source (list_recent_uoinks or search_uoinks). The description adds no further detail on the parameter, so the schema does the work and baseline 3 applies.

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?

States a specific verb and resource: 'Classify a saved capture's opening' and 'replace its stored hook analysis.' It also explicitly differentiates from siblings by naming get_taxonomy and classify_facets and what they do instead.

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?

Explicitly says 'Use to run the classifier' and names the two sibling alternatives with their distinct purposes (get_taxonomy to inspect, classify_facets to store your own labels). When/when-not guidance is complete.

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