List saved Hydra sketches with names, tags, save times, block names, and thumbnails. Filter results by entering a word that matches a sketch's name or tags.
List saved sketches: name, tags, when saved, block names, and the thumbnail path.
query filters by a word in the name or tags.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds the query filtering behavior and the kind of content returned, but does not disclose extra behavioral details such as pagination, ordering, or access requirements.
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 front-load the core purpose and returned fields, then clarify the filter. There is no filler or repetition of the schema.
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?
This is a simple read-only list tool with one optional parameter and an output schema. The description covers what the tool lists and how the query affects results; nothing essential is missing for invoking 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?
The input schema gives only the parameter name and default, with 0% schema description coverage. The description compensates by explicitly explaining that `query` filters by a word in the name or tags, which is meaningful semantic guidance.
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 starts with a specific verb and resource: 'List saved sketches', and then enumerates the returned fields (name, tags, when saved, block names, thumbnail path). This clearly distinguishes it from siblings like hydra_sketch, hydra_save, and hydra_load.
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 implies usage for browsing or listing saved sketches and explains the optional query filter. It does not explicitly name sibling alternatives or state when not to use it, so it misses full exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.