get_flet_doc

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

Annotations declare readOnlyHint=true and destructiveHint=false, so safety is clear. The description adds paging behavior: 'Long pages are cut off with a hint for the next offset' and that the response tells the next offset. This goes beyond annotations and informs the agent of a critical non-obvious behavior (incremental fetching).

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?

Two concise opening sentences that immediately convey purpose and paging hint, followed by a tightly formatted Args block. Every sentence contributes value; there is no redundancy or filler.

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 presence of an output schema (context shows output schema: true), the description covers the tool's core behavior, parameter usage, and paging workflow. An agent has everything needed to call it correctly: how to obtain the path, how to page, and what each parameter means.

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 fully compensates. It explains doc_path with an explicit example and source ('usually obtained from search_flet_docs'), explains offset as 'Line to start from' with default and response-provided next offset, and explains max_lines as 'Maximum lines to return per call' with default. All three parameters are unambiguously documented.

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?

States a specific verb+resource: 'Fetch the Markdown documentation for a specific Flet control or topic'. Differentiates from siblings by mentioning doc_path is 'usually obtained from search_flet_docs', which implies a distinct workflow from searching. The paging mention also separates it from a one-shot fetch.

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 recommends obtaining doc_path from search_flet_docs first, and instructs to 'page through' rather than request everything, which guides usage. It does not enumerate alternative tools (e.g., get_flet_example or read_flet_source), but the context is clear enough for an agent to choose correctly.

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