get_documents

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions a limit of 100 documents per call, but omits critical details such as ordering definition, pagination mechanism, return format, or any side effects. This is insufficient for a tool with no annotation support.

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 a single sentence with no redundant wording, providing the core purpose and a key limit. However, it contains a double space typo ('most recent RSpace') and lacks structured detail, slightly detracting from clarity.

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 tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It does not clarify how page_size affects results, what 'most recent' means, or how to retrieve additional documents beyond the first page. This leaves the agent with significant unanswered questions.

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% since the description does not mention page_size. The 'up to 100 at a time' phrase hints at a limit but does not explain how page_size behaves (e.g., default, max, or how to control pagination). The description fails to compensate for the schema's lack of detail.

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 retrieves recent RSpace documents, with a specific resource (documents) and action (gets). It distinguishes itself from sibling tools like get_single_Rspace_document by indicating it handles multiple documents, and the 'up to 100 at a time' clause adds scope.

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 when needing recent documents, but does not specify when not to use it or mention alternatives. There is no exclusionary guidance, but the 'most recent' phrasing provides minimal context for typical use cases.

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