boond_documents_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get a document by ID' and does not clarify whether it returns metadata, content, or both, nor does it mention permissions, side effects, or rate limits. This is a significant gap for a tool with zero annotation coverage.

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 concise phrase with no wasted words, and it is appropriately sized for a one-parameter retrieval operation. However, the brevity comes at the cost of missing crucial differentiation and behavioral details, so it is not a full 5.

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?

The description is incomplete given the sibling tool boond_documents_download. An agent cannot tell whether 'get' retrieves metadata and 'download' retrieves content, or vice versa. Without this distinction, the description does not enable correct tool selection in the context of the sibling set.

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 schema shows a single 'id' string parameter, and the description's 'by ID' clarifies that this parameter is the document identifier. Since schema description coverage is 0%, the description provides minimal but non-trivial semantic grounding for the parameter, though it adds no detail about format, examples, or the nature of the ID.

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 'Get a document by ID' states a specific verb and resource, clearly indicating a single-document retrieval operation. It is distinct from the search siblings, but it does not explicitly differentiate from the download sibling, which is also document-focused.

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?

No usage guidance is provided. The description does not mention when to use this tool versus boond_documents_search or boond_documents_download, nor does it state any prerequisites or conditions for selecting it.

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