doc_list

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. The verb 'Lista' and the phrase 'visíveis para este agente' convey a read-only, agent-scoped operation, which is useful. However, it does not mention ordering, pagination behavior, or whether results include full content or metadata, leaving some behavioral ambiguity.

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 two short sentences with no wasted words. The main action and scope are front-loaded, and the query filter detail is placed second. Every sentence earns its place.

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?

An output schema exists, so return values need not be described. However, the missing agent_id semantics and the lack of guidance on choosing doc_list over doc_search leave the description only minimally viable for correct tool selection and invocation.

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 meaningfully explains query's filtering semantics (title, tags, hash, preview), but it does not explain agent_id, whose purpose is non-obvious, and it adds no value for limit beyond what the parameter name and default imply. This is insufficient coverage for a schema with no descriptions.

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 states a specific verb and resource: 'Lista documentos' (lists documents) with the scope 'visíveis para este agente' (visible to this agent). It also specifies that query filters titles, tags, hash, and preview, which clarifies the tool's functionality. However, it does not explicitly distinguish doc_list from sibling tools like doc_search or doc_info, so it stops short of a 5.

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 about when to use doc_list versus alternatives such as doc_search, doc_get, or doc_info. The description only explains what the tool does, not the conditions under which it should be preferred. Given the large sibling set, this is a significant gap.

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