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 the tool 'Returns whether the claim requires capabilities the document lacks,' which hints at a read-only, analytical function, but doesn't clarify permissions, rate limits, or potential side effects. For a validation tool with zero annotation coverage, this is insufficient, as it omits key operational details like error handling or performance characteristics.

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 well-structured and front-loaded, starting with the core purpose, followed by usage advice, parameter explanations, and return information. Each sentence adds value without redundancy. It could be slightly more concise by integrating the 'Args' and 'Returns' sections more seamlessly, but overall, it's efficient and clear.

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 (validation tool with 2 parameters, no annotations, but an output schema exists), the description is reasonably complete. It covers purpose, usage, parameters, and return intent. The presence of an output schema means it doesn't need to detail return values, but it could benefit from more behavioral context (e.g., error cases). Overall, it meets most needs for a tool of this type.

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 context beyond the input schema: it explains that 'document_id' refers to 'the document to validate against' and 'claim' is 'The claim or assertion to validate.' With 0% schema description coverage, this compensates well by clarifying the purpose of each parameter. However, it doesn't detail format constraints (e.g., claim length limits), keeping it from a perfect score.

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: 'Check if a specific claim can be grounded in the source document.' It specifies the verb ('check'), resource ('claim'), and context ('source document'), making the intent unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'validate_agency_execution' or 'validate_existential_response', which appear related to validation but target different aspects.

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 some usage guidance with 'Use this BEFORE making scholarly assertions,' implying a pre-emptive validation step. However, it lacks explicit when-not-to-use criteria or clear alternatives among siblings (e.g., vs. 'validate_agency_execution'). The context is implied but not fully articulated, leaving gaps in distinguishing from similar tools.

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