truthstack-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 a 'raw evidence bundle' for citation, but doesn't describe the return format (e.g., structured data, text), potential limitations (e.g., data freshness, availability), or any operational constraints (e.g., rate limits, authentication needs). This leaves significant gaps for a tool with no annotation coverage.

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 concise and front-loaded, consisting of a single sentence that directly states the tool's output and purpose. There's no unnecessary elaboration, though it could be slightly more structured (e.g., separating output from usage). Every sentence earns its place by conveying core information efficiently.

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 of retrieving evidence data (involving multiple data types like FAERS and CYP), no annotations, and no output schema, the description is incomplete. It lacks details on the return structure, data sources, reliability, or how the evidence bundle is formatted, which are critical for effective tool use in a medical/contextual domain.

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 schema description coverage is 100%, with both parameters ('supplement' and 'drug') clearly documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as format examples or interdependencies. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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: retrieving a 'raw evidence bundle' containing specific data types (FAERS counts, CYP data, research grades, label warnings) for citation purposes. It uses a specific verb ('get') and resource ('evidence bundle'), though it doesn't explicitly distinguish itself from sibling tools like 'get_compound_info' or 'search_compounds' which might also retrieve related information.

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 minimal usage guidance, only stating the tool is 'for citing sources.' It doesn't specify when to use this tool versus alternatives like 'get_compound_info' or 'search_compounds,' nor does it mention prerequisites, exclusions, or contextual triggers for its use.

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