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. However, it reveals nothing about the tool's behavior—such as whether it's read-only or destructive, its authentication needs, rate limits, or output characteristics. This is inadequate for a tool with unknown behavioral traits, especially without an output schema to clarify results.

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?

While concise, the description is under-specified rather than efficiently informative. 'DataProcessor tool description' is a placeholder-like phrase that fails to convey essential details, making it ineffective despite its brevity. Conciseness should not come at the cost of clarity, and this description does not earn its place with useful content.

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 lack of annotations and output schema, the description is severely incomplete. It does not explain what the tool does, when to use it, behavioral traits, or output expectations. For a tool named 'data-processor' with one parameter, this minimal description leaves critical gaps, making it inadequate for an AI agent to understand and invoke the tool 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?

The input schema has 100% description coverage, with the 'message' parameter documented as 'Message to process'. The description adds no additional meaning beyond this, but the schema provides sufficient baseline information. With high schema coverage and only one parameter, a score of 3 reflects adequate but minimal parameter semantics from the schema alone.

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 'DataProcessor tool description' is a tautology that merely restates the tool name with minimal elaboration. It fails to specify what the tool actually does (e.g., what 'process' entails), what resource it operates on, or how it differs from sibling tools like 'file-handler' or 'api-client'. This provides no meaningful guidance for an AI agent to understand the tool's function.

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 offers no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, nor does it reference sibling tools like 'file-handler' or 'api-client' that might handle related tasks. This leaves the agent with no information to make an informed selection among available tools.

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