roiq_overview

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

No annotations are provided, yet the description does not mention any behavioral traits such as being read-only, potential side effects, or performance implications. The overview nature hints at read-only access, but this is not explicitly stated, which is a gap given the lack of annotations.

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 extremely concise with two sentences. The first sentence front-loads the purpose, and the second provides clear usage guidance. Every word serves a purpose.

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 no output schema and no annotations, the description provides the basic purpose and usage guidance. However, it lacks details on the return format or any caveats. For a simple overview tool, it is minimally adequate but could benefit from specifying what data is returned.

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?

There are no parameters, and schema description coverage is 100%. The description does not need to add parameter information. With zero parameters, the baseline is 4, and the description adds no confusion.

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 it provides an overview of the workspace, including spaces, item counts by type, and sections with data. The verb 'Resumen' (overview) effectively distinguishes it from sibling tools that perform specific operations like creating or listing items.

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?

Explicitly says 'Úsala primero para orientarte' (Use it first to orient yourself), providing a clear when-to-use recommendation. It doesn't explicitly mention alternatives but considering the sibling tools, the context implies this is the starting point for orientation.

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