suggest_flyte_plugin_for

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

Discloses V2 prioritization behavior but does not mention read-only nature, auth, rate limits, or error handling. No annotations to rely on.

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 sentences with no fluff; first sentence provides purpose, second adds key behavioral nuance.

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?

Covers purpose and key behavioral preference. Missing details on limit param and return structure, but output schema exists. Adequate for a simple suggestion tool.

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?

Describes 'need' as natural-language query but does not describe 'limit' parameter. Schema coverage is 0%, so description partially compensates.

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?

Clearly states verb (suggest), resource (plugins), and natural-language input. Differentiates from sibling list/get plugins.

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?

Indicates preference for V2 plugins but does not explicitly state when to avoid or use alternative tools like list_flyte_plugins or get_flyte_plugin.

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