OSINT MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool enriches data using Apollo.io but does not cover critical aspects such as rate limits, authentication needs, data accuracy, privacy implications, or what happens on partial matches. This leaves significant gaps for an OSINT tool.

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 appropriately sized and front-loaded, with the core purpose stated first ('Enrich person data using Apollo.io - find email, title, social profiles.') followed by a parameter list. It avoids unnecessary details, though the parameter explanations are minimal and could be more efficient.

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 complexity (OSINT tool with 4 parameters, no annotations, but an output schema exists), the description is moderately complete. It covers the basic purpose and parameters but lacks behavioral context and usage guidelines. The presence of an output schema means it doesn't need to explain return values, but other gaps remain, making it adequate but with clear room for improvement.

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 lists the parameters (first_name, last_name, organization, domain) and briefly explains them (e.g., 'Person's first name'), but does not add meaningful semantics like format constraints, examples, or how parameters interact (e.g., if domain is required when organization is provided). This provides basic clarification but falls short of fully compensating for the lack of schema descriptions.

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's purpose: 'Enrich person data using Apollo.io - find email, title, social profiles.' It specifies the verb ('enrich'), resource ('person data'), and data sources (Apollo.io), but does not explicitly differentiate it from sibling tools like 'osint_person_research' or 'osint_email_finder', which likely have overlapping functions.

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?

No guidance is provided on when to use this tool versus alternatives. The description lists what it does but does not mention when it should be used, prerequisites, or exclusions, despite having many sibling tools that might serve similar purposes (e.g., 'osint_person_research', 'osint_email_finder').

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