InsightSentry MCP

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

Since no annotations exist, the description carries the full burden. It excellently compensates for the missing output schema by providing the complete return structure inline. It also discloses default behavior (current week) that is not visible in the input schema.

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?

Despite being dense due to the inline JSON return structure, every element serves a critical purpose. Information is front-loaded with the purpose statement, followed by return schema, defaults, and parameter usage. The inline JSON is necessary given the lack of structured output 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?

Given the lack of annotations and structured output schema, the description provides comprehensive coverage by including the return type structure, default behaviors, and parameter filtering capabilities. It adequately prepares an agent to invoke the tool successfully.

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?

With 100% schema description coverage, the baseline is 3. The description largely restates schema content (e.g., 'NASDAQ:AAPL' example duplicates schema). It adds 'Default: current week' which is behavioral context for the 'w' parameter, but does not significantly expand on parameter semantics beyond the schema definitions.

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 it retrieves 'earnings calendar data' with a specific time range scope. The prefix 'Earnings calendar' distinguishes it from sibling tools like get_dividends, get_ipos, and get_events by specifying the exact financial dataset.

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 implied usage guidance through default behavior ('Default: current week') and parameter hints ('Use 'w' to look ahead'), but lacks explicit guidance on when to choose this over get_events or get_fundamentals_series for earnings-related data.

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