search_flet_docs

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds behavioral context beyond that: the tool returns the correct file path to feed into get_flet_doc, and it surfaces intent/cookbook content rather than exact API details.

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 three short, purposeful sentences plus a one-line parameter definition. The primary purpose is stated first, and the workflow guidance and source-tool distinction are both delivered without wasted words.

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 single-parameter, read-only search tool with an output schema, the description is complete. It names the intended workflow (search first, then get_flet_doc), clarifies what docs offer versus source tools, and provides parameter guidance plus examples.

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 provides only a 'query' property with the title 'Query' and no description, so schema coverage is effectively 0%. The description compensates by defining the parameter as 'The keyword to search for' and supplying concrete examples like 'dropdown', 'navigation', and 'layout'.

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 opens with a specific verb and resource: 'Search the official Flet documentation index for a specific topic or control.' It clearly states what the tool does and how it differs from source tools by saying 'Docs explain intent and cookbook patterns; use the source tools for exact APIs.'

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 gives explicit usage context: 'Always use this first to find the correct file path before calling get_flet_doc.' It also tells the agent when not to rely on this tool—when exact APIs are needed, use source tools—so routing between siblings is clear.

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