InsightSentry MCP

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

No annotations provided, but description carries the burden well by disclosing dual return formats (JSON vs binary), PDF text extraction behavior, and the dependency on get_documents. Lacks rate limit or error handling details.

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?

Suffers from noticeable repetition: 'Retrieve a specific document' appears twice, and return format documentation is duplicated (before and after the arrow symbol). Information is front-loaded but could be consolidated into fewer sentences.

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?

Compensates well for lack of output schema by detailing return structures ({title, published_at, content}) and format variations. Covers the 4-parameter complexity adequately with workflow context and PDF handling specifics.

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 has 100% coverage, establishing baseline 3. Description adds significant value beyond schema by strongly recommending text=true for readability and explaining the id/code workflow dependency, which aids agent decision-making.

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?

Clearly states the tool retrieves a specific document's content and explicitly distinguishes itself from sibling 'get_documents' by stating 'Get document IDs from get_documents first,' establishing the list-then-retrieve workflow.

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?

Provides clear workflow guidance (obtain IDs from get_documents first) and strong operational recommendations (**Always use text=true**). Lacks explicit 'when-not-to-use' exclusions (e.g., for listing/browsing), though this is partially implied.

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