flutter_find_sample

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

With no annotations provided, the description carries the full burden. It discloses the return behavior ('Returns the best-match sample in full with gotchas'), which is valuable and beyond what the schema conveys. It also notes the corpus is 'verified,' implying quality guarantees. Slightly under-discloses search-failure behavior or the exact meaning of 'best-match,' but the core behavioral contract is clear.

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?

Compact two-sentence description with strong front-loading ('FIRST STOP' immediately signals purpose). The topic enumeration is useful but slightly long, listing 9 areas. No wasted words, though the large parenthesis list edges toward over-specification for a first-line description. Efficient overall.

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 a single simple parameter, 100% schema coverage, and no output schema, this description is complete. It states the purpose, when to use it, what the input should contain, and what the return is. Nothing material is left unsaid for an agent to use this tool 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 schema covers 100% of the single parameter with a clear example ('animated chart with custom painter', 'background json parsing'). The description adds consistent context that the 'need' parameter should describe what you're building, aligning with and reinforcing the schema example. Essentially no additional meaning beyond schema, but schemas already carry the full burden at 100% coverage, so baseline 3 is appropriate.

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 is highly specific: 'FIRST STOP when writing advanced Flutter code' with explicit verb (search) and resource (verified sample corpus), and enumerates the covered topics (custom render objects, shaders, slivers, animation physics, isolates, platform channels, etc.). It clearly differentiates from siblings like flutter_get_sample and flutter_list_samples by positioning itself as the first-stop search tool.

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 frames WHEN to use it ('FIRST STOP when writing advanced Flutter code') and HOW to invoke it ('by describing what you're building'). The enumerated topic list and 'verified sample corpus' signal specificity versus the broader flutter_docs or dart_docs siblings. The covered-technique list acts as implicit exclusions—if your need isn't in that list, a different tool is likely appropriate.

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