BigContext MCP

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 pagination via 'offset' but does not cover critical aspects like rate limits, authentication needs, error handling, or whether the operation is read-only or has side effects. For a list operation with zero annotation coverage, this is a significant gap in transparency.

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: the first sentence states the purpose clearly, followed by structured 'Args' and 'Returns' sections. Every sentence earns its place without redundancy, making it efficient and easy to parse.

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 low complexity (2 parameters, no nested objects) and the presence of an output schema (implied by 'Returns'), the description is somewhat complete but has gaps. It covers basic purpose and parameters but lacks behavioral context and usage guidelines, which are important for a tool with no annotations. The output schema handles return values, but overall completeness is minimal viable.

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 description adds meaningful semantics beyond the input schema, which has 0% description coverage. It explains that 'limit' controls the maximum number of documents returned with a default, and 'offset' is for pagination to skip documents. This compensates well for the schema's lack of descriptions, though it could detail format constraints (e.g., integer ranges).

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: 'List all indexed documents with their metadata.' This specifies the verb ('List'), resource ('indexed documents'), and scope ('all'). However, it does not differentiate from sibling tools like 'get_metadata' or 'search_segment', which might have overlapping functions, so it misses full sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. It lacks explicit context, exclusions, or references to sibling tools such as 'search_segment' for filtered searches or 'get_metadata' for specific metadata retrieval, leaving usage ambiguous.

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