Unified Salesforce Documentation MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions handling iframes/structures and returning markdown, which adds some context about processing behavior. However, it lacks critical details like authentication requirements, rate limits, error handling, or whether this is a read-only operation (implied by 'scrape' but not explicit).

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 concise with two sentences that efficiently convey the core functionality and output format. It's front-loaded with the main purpose, though it could be slightly more structured by separating behavioral details from the core statement.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete for a scraping tool with two parameters. It covers the basic purpose and output format but misses parameter explanations, error conditions, authentication needs, and detailed behavioral context that would help an agent use it correctly.

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 for undocumented parameters. It doesn't explain the 'url' parameter (beyond implied Salesforce docs) or the optional 'category' parameter at all. The description adds minimal meaning beyond what the bare schema provides, failing to address the coverage gap.

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: 'Scrape a single Salesforce documentation page' with specific resources (developer.salesforce and help.salesforce pages) and output format (markdown). It distinguishes from siblings by focusing on single-page scraping rather than mass extraction or local search, though it doesn't explicitly name the alternatives.

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 implies usage context by specifying Salesforce documentation pages and handling iframes/structures, suggesting when this tool is appropriate. However, it doesn't provide explicit guidance on when to use this versus the sibling tools (mass_extract_guide, search_local_docs) or any exclusion criteria.

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