Get a single Mudbase document

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

No annotations are provided, so the description carries the full burden. 'Fetch' clearly signals a read-only operation, but the description does not go beyond that to mention not-found behavior, authentication, or the shape of the returned document.

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?

A single sentence that is front-loaded with the action and resource, with no filler or redundancy. It earns its place and leaves the schema to handle parameter detail.

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 simple ID-based read with a fully described schema and no complex output, the description is nearly sufficient. It could add a note about when to prefer list_documents, but an agent can already determine parameters from the schema and infer the return value from 'Fetch a single document'.

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?

All three parameters are already described in the input schema (projectId, collectionId, documentId), so the schema carries the semantic weight. The description adds no per-parameter detail or relationship among the IDs, matching the baseline for high schema coverage.

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 uses a specific verb ('Fetch'), a precise resource ('a single document by ID'), and an explicit container ('from a Mudbase collection'). 'Single' distinguishes it from list_documents and search_documents, while 'by ID' separates it from collection-level operations.

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 intended use is implied: call this when you already have an ID and need one document. However, it never names alternatives like mudbase_list_documents or says when not to use this tool, so an agent gets no explicit routing guidance.

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