krita_list_brush_presets

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safe read-only behavior is covered. The description adds useful context about scope ('current instance') and the result resource ('handles'), but does not disclose additional behavior such as return format or whether query matching is fuzzy or exact.

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 concise sentence with no filler. The key action 'Search and paginate' is front-loaded, and every phrase adds meaningful information about scope and resource.

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?

For a simple list/search tool, the description is minimally viable, but it leaves gaps: there is no output schema, no explanation of what a 'brush preset handle' is or how it relates to krita_inspect_brush, and no detail about query behavior or pagination semantics. Annotations cover side-effect safety, so this is acceptable but not complete.

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 0%, so the description must compensate for missing parameter documentation, but it does not. 'Search' and 'paginate' weakly map to query, limit, and offset, but no parameter-level meaning is provided for instance_id, limit, offset, or query.

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 states a specific action ('Search and paginate') and a clear resource ('the current instance's brush preset handles'). It also scopes the operation to the current instance, and the resource 'brush preset handles' clearly distinguishes it from sibling listing tools such as krita_list_documents and krita_list_diffusion_jobs.

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?

There is no guidance about when to use this tool instead of alternatives like krita_inspect_brush, nor any mention of exclusions or prerequisites. The description only states what the tool does, leaving the agent to infer when it is appropriate.

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