InsightSentry MCP

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

With no annotations provided, the description carries full disclosure burden and notably includes the complete return structure schema (→ Returns {...}), revealing the data shape, field types, and nesting. However, it omits rate limits, caching behavior, or explicit read-only safety declarations.

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?

Information-dense and efficiently structured using the arrow symbol (→) to separate action from return value. The front-loaded 'IPO calendar' fragment and compact JSON return specification maximize information per token, though the return type string is lengthy.

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?

Adequately compensates for the missing output schema by detailing the return structure inline, and covers the primary filtering parameters. For a read-only retrieval tool with four optional parameters, the description provides sufficient context for correct invocation despite minor gaps (filter param, rate limits).

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 coverage is 100%, establishing baseline 3. The description adds value by providing a concrete example ('NASDAQ:AAPL') for the 'code' parameter and simplified usage guidance for 'w' and 'c'. It fails to mention the 'filter' parameter (JSONata expression) in the prose, though the schema documents it.

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 tool retrieves 'IPO calendar data' (specific verb + resource) and specifies the time range scope. 'IPO calendar' distinctly identifies this tool's domain among financial data siblings like get_dividends and get_earnings.

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 useful default context ('Default: current week') and hints for parameter usage ('Use 'w' to look ahead'), but lacks explicit guidance on when to prefer this over similar market data tools like get_earnings or get_events, and doesn't specify prerequisites or constraints.

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