Prysm 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 'fewer scrolls' and 'main content only', which gives some context about limitations, but doesn't cover important aspects like error handling, rate limits, authentication needs, or what 'main content' specifically means. The description is insufficient for a mutation tool with zero 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 extremely concise with just one sentence that efficiently communicates the core value proposition. Every word earns its place, and it's front-loaded with the key information about speed optimization.

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?

For a web scraping tool with 9 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, how it handles errors, what 'main content' means, or provide sufficient behavioral context for proper usage.

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 100%, so the schema already documents all 9 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline is 3 when schema does the heavy lifting.

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 as 'Fast web scraping optimized for speed' and specifies it focuses on 'main content only', which distinguishes it from generic scraping. However, it doesn't explicitly differentiate from sibling tools like scrapeBalanced or scrapeDeep beyond the speed optimization hint.

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 for speed-focused scraping with limited content extraction, but doesn't explicitly state when to use this tool versus alternatives like scrapeBalanced or scrapeDeep. No guidance on exclusions or prerequisites is provided.

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