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

Annotations already mark the tool as readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the 'full text content' behavior, but does not disclose potential batch limits beyond the schema, error conditions, or return format. With annotations doing heavy lifting, this is adequate but not enriched.

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, focused sentence with no filler. It front-loads the core action and object, and every word contributes to understanding the tool's purpose.

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?

Given the tool's simplicity (one parameter, no output schema) and the annotations, the description provides sufficient context to invoke it correctly. It does not describe response structure, but that is less critical for a retrieval tool, and the schema covers the input. The only minor gap is lack of guidance about how to obtain IDs, which would push it to a 5.

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 schema description covers the parameter well, stating it takes santiment crypto insights IDs with a max of 10. The tool description adds no further semantic detail. The schema's oneOf allowing a string is ambiguous (comma-separated? JSON-encoded?), and neither the description nor schema clarifies it, so the baseline 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 clearly states the action ('Fetch full text content') and resource ('specific santiment crypto insights IDs'), distinguishing it from sibling tools like insight_discovery_tool which likely handle discovery rather than retrieval by ID. The verb+resource combination is specific and unambiguous.

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 establishes a clear usage context: this tool is for retrieving full content for already-known insight IDs. It does not explicitly mention that insight_discovery_tool should be used first to find IDs, nor does it list exclusion criteria, but the intent is clear enough for an agent to select it appropriately.

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