Find QML Translations

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is covered. However, the description adds nothing beyond stating what is searched – no mention of scope (single file vs directory tree), no output format, no behavioral context about the 'path' parameter's effect.

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?

One short, efficient sentence with no filler. It is front-loaded and readable, though extremely terse given the tool's search behavior.

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 search tool with an undocumented search-scope parameter and no output schema, the description leaves significant gaps: what 'path' means (file vs directory), whether the search is recursive, and what the result looks like.

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 50%; 'timeout' is documented in the schema while 'path' has no description anywhere. The description does not compensate for the undocumented 'path' parameter.

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 (Find) and resource (qsTrId and translator comments in QML files), which is clear and distinguishable from most siblings. It doesn't explicitly differentiate from sailfish_qml_check_translator_ternaries, the closest sibling, but the scope is specific enough to select the 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?

No when-to-use guidance, no prerequisites, and no mention of the alternative sibling sailfish_qml_check_translator_ternaries. The agent must infer usage entirely.

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