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

Annotations only establish read-only/non-destructive, and the description adds substantially more: fabricated names fail on real devices, typed signatures outrank worked examples that are explicitly not typechecked, and results carry `traps` for known field gotchas. This is exactly the kind of consequence and reliability context annotations cannot express.

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?

Front-loaded with what the tool returns, then usage modes, then the authority caveat and traps note — no filler sentences. The prose is dense and could be split with the parameter modes listed tersely, but every sentence carries information an agent needs.

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, the description does mention the shape of results in part (traps) and where the data comes from, and it addresses the conflicting-authority problem that could otherwise mislead an agent. It stops short of describing overall result structure or limits, which is a minor gap for a read-only reference 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?

Schema description coverage is 0% across 8 parameters, so the description carries the full burden and largely meets it by explaining the intent behind method/entity/topic/field/query and the plural batch variants. It does not say what happens when multiple lookup keys are combined or how query matching works, leaving some ambiguity.

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 with unusual precision: 'version-locked command-frame API' covering renderClient signatures, CF* entity fields, pub/sub topics, and examples. The scope is narrow enough that an agent can tell it apart from the sibling lookup tools (flow_lookup_pos_api, flow_lookup_engine_component) by subject matter.

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?

Gives a clear triggering condition ('ground every renderClient call in this before writing it — fabricated fields/methods fail on real Render devices') and maps each parameter mode to a distinct intent: single key for precise lookup, entity+field for existence checks, query for fuzzy search, plurals for batch. It never names or contrasts the sibling lookup tools, so the agent must infer which lookup to reach for.

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