flo_qc_logo

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

No annotations exist, so description must disclose behavioral traits. It does not mention whether the tool is read-only, destructive, requires authentication (authToken parameter suggests auth needed but not stated), or what side effects occur.

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?

Single sentence with no structure; while concise, it omits essential details. Could be expanded to include parameter hints or behavioral notes without losing conciseness.

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?

With no output schema, no annotations, and vague parameter guidance, the description fails to equip an agent to use the tool correctly. Missing information on returns, prerequisites, and error conditions.

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% (only includePdf and authToken have descriptions). The description adds no explanation for the critical parameters assetId and referenceAssetId, which are required. 'Stored-image reference mode' hints at referenceAssetId but is insufficient.

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?

Description specifies the verb 'Run' and the endpoint '/flo:qc-logo' along with mode 'stored-image reference mode' and context 'Claude plugin happy path'. This is specific enough to differentiate from generic tools, though jargon may obscure exact functionality for newcomers.

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 guidance on when to use this tool versus its siblings (e.g., flo_analyze, flo_happy_path_run). No conditions or exclusions provided.

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