nexo_system_catalog

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

With no annotations, the description must disclose behavioral traits but only states it is a 'Read' operation. It does not mention any side effects, pagination behavior, limit semantics, or authorization requirements. The agent cannot predict key behavioral aspects.

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 sentence, concise and to the point. It is easily readable, but could benefit from a structured format like bullet points to separate usage hints or parameter explanations.

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 three parameters with no documentation, no output schema, and no annotations, the description is insufficient. It fails to explain what the output contains, how parameters influence results, or any constraints. The agent cannot reliably use this tool.

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% and the description adds no explanation for the three parameters (limit, query, section). Their meaning, format, and interaction are completely opaque, forcing the agent to guess or fail.

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 tool reads a live system catalog built from various NEXO components, distinguishing it from sibling tools that handle automation, memory, checkpoints, etc. The verb 'Read' and resource 'system catalog' are specific and unambiguous.

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 like nexo_local_index_status or nexo_memory_search. The agent has no context to decide whether this catalog is appropriate for a given query.

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