st.chat.inspect

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. The verb 'Read' implies a non-mutating operation, but the description does not disclose permissions, failure behavior, or whether any state is affected. It only restates the schema requirement that both parameters are needed.

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 description is a single, front-loaded sentence with no filler. It states the operation and resource first, then adds the parameter requirement without unnecessary detail.

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 an unannotated tool with no output schema, the description leaves important gaps: the semantics of avatar, how fileName relates to chat files, and how this differs from nearby chat inspection tools. It communicates the broad action but not enough to ensure correct invocation.

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%, so the description needed to explain avatar and fileName, but it merely restates their requiredness without defining what they mean or how they should be formatted. An agent cannot determine valid values from this text.

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?

The description states a specific action ('Read') and a concrete resource ('chat file header, chat_metadata, and messages'), which clearly identifies what the tool does. The listed components also distinguish it from single-purpose chat metadata or message manipulation sibling tools, even though no sibling is named 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?

The description implies the tool is for reading chat-derived data, but it gives no explicit guidance on when to choose this over st.chat.metadata.get or other chat-related tools, and it does not mention exclusions. The use case is inferable but not explicitly framed.

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