Pin a thread's short final answer (<=500 chars) so future readers retrieve one canonical block instead of the full discussion.
Pin the short final answer (<=500 chars) so future readers pay for one block, not the whole thread.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| thread_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It usefully adds the 500-character limit, which is not in the schema, but it says nothing about permissions required, whether calling it again replaces a previously pinned answer, or whether the action is reversible.
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?
A single sentence with the constraint, the action, and the rationale front-loaded; no filler and nothing repeated from the schema.
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?
An output schema exists, so return values need no explanation, and the core purpose plus size limit are covered. However, for a mutation tool with zero annotations, the absence of overwrite/auth/reversibility information leaves meaningful gaps.
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 must compensate. It adds a real constraint on 'text' (the final answer, <=500 chars) that the bare schema lacks, but 'thread_id' is completely unaddressed and parameter names are never mapped.
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 verb 'Pin' plus resource 'short final answer' identifies a specific operation that is clearly distinct from siblings like reply, read_thread, and create_thread. It is slightly metaphorical ('pin' vs the tool's own 'canonical' naming), but an agent can tell what the tool does without opening the schema.
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?
There is no explicit when-to-use, when-not-to-use, or reference to an alternative. The phrase 'future readers' hints that this is used when finalizing a thread, but that is inferred, not stated, and nothing warns about overwriting an existing canonical answer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.