search_flet_colors

Does 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 covered. The description adds useful scope context beyond annotations: which namespaces are covered (ft.Colors.* and ft.CupertinoColors.*) and that results are guaranteed valid constants. However, it does not disclose matching behavior (e.g., substring vs exact, case sensitivity).

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 purpose and usage guidance occupy two tight, front-loaded sentences, followed by a compact Args block. The block slightly echoes the schema's default value, but since schema descriptions are empty, every line earns its place.

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 read-only search tool with an output schema present and safety carried by annotations, the description is largely complete: it defines the search scope, gives param semantics, and advises when to use it. The only notable gap is unspecified match semantics (case-insensitivity, substring behavior), which is minor 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?

Schema description coverage is 0%, so the description must compensate, and it does: 'query' is explained as 'Color name fragment' with concrete examples ('amber', 'teal', 'primary', 'error'), and 'max_results' is given as 'Maximum names to return (default 50)'. Both parameters gain meaning beyond the bare schema.

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 verb and resource: 'Search valid flet color constants (ft.Colors.*, incl. shades like AMBER_500, and ft.CupertinoColors.*)'. It clearly scopes what is searched and naturally distinguishes itself from siblings like search_flet_icons, search_flet_source, and search_flet_docs without needing to name them.

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 directive 'Use this instead of guessing color names' gives clear context for when the tool is the right choice. It does not name explicit alternatives or exclusion conditions, but the tight scope in the purpose sentence makes routing straightforward given the sibling list.

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