RSpace MCP Server

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

No annotations are provided, so the description carries full burden. It mentions 'Downloads file attachments' and 'Returns: Download status and file information', which indicates a read operation with output. However, it doesn't disclose critical behavioral traits: whether this requires specific permissions, if it overwrites existing files at 'file_path', rate limits, error conditions, or what 'Download status' entails. For a file-writing tool with zero annotation coverage, this is insufficient.

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 well-structured with clear sections (purpose, usage, parameters, returns) and front-loaded key information. Every sentence earns its place, though 'Returns: Download status and file information' could be more specific. It's appropriately sized for a 2-parameter tool without being verbose.

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 2 parameters with 0% schema coverage and no output schema, the description provides basic purpose, usage, and parameter semantics. However, for a tool that writes to the local filesystem, it lacks details on permissions, file overwriting behavior, error handling, and output format. With no annotations and no output schema, the description is adequate but has clear gaps in behavioral context.

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. It adds meaning beyond the bare schema by explaining 'file_id: Numeric ID of the file attachment' and 'file_path: Local filesystem path where file should be saved'. This clarifies the purpose and format of both parameters, though it doesn't detail constraints (e.g., valid ID ranges, path syntax). Given 2 parameters, this provides good semantic context.

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: 'Downloads file attachments from RSpace documents' with specific verb ('Downloads') and resource ('file attachments from RSpace documents'). It distinguishes this from sibling tools like 'uploadAndAttachFile' by focusing on retrieval rather than upload, though it doesn't explicitly name 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 'Usage' section provides context: 'Retrieve images, data files, or other attachments', which implies when to use this tool. However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings (e.g., 'get_documents' might retrieve metadata without files). The guidance is implied rather than explicit.

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