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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the singular scope ('one user transcript') and the HTTP method (POST), but does not disclose return format, error behavior, authentication needs, or rate limits. It aligns with annotations and adds minimal context beyond them.

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 concise sentence that directly states the action, resource, endpoint, and parameter. It is front-loaded with the verb 'Fetch', contains no unnecessary words, and every element is relevant.

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 simple read-only tool with one parameter and an output schema present, the description provides sufficient context: it specifies what is fetched (one user transcript), how (POST /v1/get-chat), and using which parameter (end-user fbId). Return values are covered by the output schema, so no further explanation is needed.

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 input schema already describes the only parameter fbId with a clear description ('End-user fbId whose transcript you want'), achieving 100% schema coverage. The description repeats 'using the end-user fbId' without adding format, constraints, or additional meaning, so the baseline score of 3 is appropriate.

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 uses the specific verb 'fetch' and identifies the resource as 'one user transcript', clearly distinguishing it from sibling tools like list-conversations or get-converse-history by emphasizing the singular nature and the fbId-based retrieval. The mention of the POST endpoint adds further specificity.

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?

Usage context is implied by the phrase 'one user transcript' and the fbId parameter, suggesting it is for retrieving a single user's chat transcript. However, there is no explicit guidance on when to use this tool instead of alternatives like list-conversations or get-converse-history, nor any exclusions or prerequisites.

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