list_flet_controls

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

No annotations are provided, so the description must convey behavior. It describes the tool as returning a 'complete list', implying a read-only, non-destructive operation. While it doesn't explicitly state safety characteristics, the nature of listing controls is clearly a safe query, so the description is adequate.

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 consists of two short sentences with no wasted words. Every sentence adds value: the first defines the action, the second gives usage context.

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 the tool's simplicity and the presence of an output schema (which explains return values), the description is complete. It covers what the tool does and when to use it, meeting all needs for a straightforward listing operation.

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 tool has zero parameters and the schema coverage is 100%. According to the rubric, zero parameters gives a baseline of 4. The description adds no parameter details, which is acceptable here.

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 uses a specific verb 'Get a complete list' and specifies the resource 'Flet UI controls', clearly distinguishing it from sibling tools like get_flet_doc or search_flet_docs which deal with documentation rather than a list of controls.

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 explicitly states 'Use this to discover what UI elements can be built in Flet', providing clear context for when to use the tool. It does not, however, provide explicit exclusion criteria or mention alternative tools.

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