get_flet_version

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

The description explains that the tool reports both the version and the source location, and gives the important rationale that Flet changes faster than training data so the installed source is the only truth. This adds meaningful context beyond the readOnlyHint and destructiveHint annotations, and there is no contradiction.

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 two concise sentences with no filler. The core purpose is front-loaded, and the usage guidance follows immediately with a clear rationale.

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 parameterless read-only tool with an output schema, the description fully covers what the tool does, when to use it, and why it matters. Nothing essential is missing for an agent to invoke it 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 tool has zero parameters, so the input schema is trivially complete and the description does not need to explain parameter behavior. The baseline for parameter-free tools is 4, and the description adds no unnecessary parameter details.

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 and resource: 'Report which flet version the source tools read, and from where.' This clearly identifies the tool's exact function and is distinct from sibling tools that inspect, search, or verify Flet code.

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 says 'Call this first when a Flet API question matters', giving clear guidance on when to invoke it. It does not enumerate when-not-to-use conditions or alternatives, but the 'first' instruction provides strong contextual usage direction.

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