get_documents

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

No annotations exist, so the description must fully convey behavioral traits. It merely states the action without mentioning pagination behavior (offset), authorization requirements, rate limits, or whether the list is comprehensive or filtered. The schema includes pagination and organization filters, but the description does not address them.

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 short sentence, which is efficient but lacks essential details. Given the absence of annotations, it should convey more context to be useful. It is front-loaded but insufficiently informative.

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?

With three parameters, no output schema, and no annotations, the description is too sparse. It does not explain return values, pagination limits, or how the organization filter interacts with projectIds. The tool is simple but the description omits critical usage details.

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 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; it does not explain how parameters like 'organization' or 'offset' modify the result set. The description's role is fulfilled by the schema, but it misses an opportunity to clarify usage.

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 action ('Gets a list of documents') and the resource ('in a project'). It distinguishes from siblings like 'get_document' or 'addDocument', though it could explicitly tie the project scoping to the required 'projectIds' parameter.

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 guidance is provided on when to use this tool versus alternatives such as 'get_document' (single document) or 'get_document_tree' (hierarchical view). There are many sibling tools, and the description fails to indicate context or exclusions.

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