Pollinations Multimodal MCP Server

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 states the tool checks authentication session status but fails to describe what the check entails (e.g., returns validity, expiration, user info), any side effects, error conditions, or response format. The stylistic advice adds no behavioral value, leaving significant gaps.

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 poorly structured and not front-loaded; it buries the tool's purpose in the first sentence and spends most of the text on irrelevant stylistic instructions (e.g., 'use Gen-Z language with emojis'). This wastes space and detracts from clarity, making it inefficient and unfocused.

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 and no output schema, the description is incomplete for a tool that likely returns session status details. It lacks information on what the check returns (e.g., valid/invalid, metadata), error handling, or prerequisites, failing to provide necessary context for effective use.

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%, with the single parameter 'sessionId' documented as 'The session ID to check.' The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating further.

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 'Check the status of an authentication session,' which is a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'startAuth' or explain how this differs from other authentication-related operations, keeping it from a perfect score.

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 like 'startAuth' or other sibling tools. It only includes stylistic instructions for responses, which are irrelevant to tool selection and usage, offering no practical context for decision-making.

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