render_in_chat

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

With no annotations, the description carries the behavioral disclosure burden and does so well: it discloses that the card is a server-generated self-contained snapshot, does not connect to serve, contains no secrets, and renders in a sandboxed iframe. It does not explicitly state read-only/no-mutation, but 'render' plus snapshot semantics strongly imply no live state changes.

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 core behavior is front-loaded in the first sentence, followed by concise implementation and security caveats. The bracketed references [9-D] and [11] are internal documentation artifacts that add little agent-usable meaning, but the overall length is reasonable and dense.

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 one-parameter render tool with an output schema present, the description covers the client context, display mode, snapshot behavior, and security properties. A slight gap is the lack of an explicit side-effect or read-only statement, but the wording makes accidental mutation unlikely.

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 only parameter, node_id, has 0% schema description coverage, so the description must compensate. It does so by making clear that the node identifies the entity whose neighboring subgraph will be rendered. It could explicitly name node_id, but the semantic intent is unambiguous.

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 a concrete action—rendering the target node's neighboring subgraph as an interactive chat card—and identifies the medium (sandboxed iframe for MCP Apps clients). It is clearly distinguishable from data-returning siblings such as get_neighbors or export_graph, though it never names a sibling explicitly.

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?

It gives useful context about where rendering happens (chat iframe in MCP Apps clients) and contrasts with the full live view being in a separate browser window, which is an implicit routing signal. However, it does not explicitly say when to choose this tool over alternatives or state exclusions.

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