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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false. Beyond that, the description adds auth requirements, cost (free), refresh behavior via meta.catalog_version, and how newly added tools can be used, which is meaningful operational context beyond the structured 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 front-loaded with "Start here" and uses short, purposeful sentences for refresh behavior, return contents, auth, and run_tool fallback. Every sentence adds operational value without repetition.

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?

For a zero-parameter read-only discovery tool with no output schema, the description covers when to call, what it returns, authentication needs, refresh triggers, and the fallback path for newly added tools. Nothing essential for correct invocation is missing.

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 tool has zero parameters, so there are no parameter semantics to explain. With 0 parameters, the baseline is 4; the description correctly does not invent or discuss nonexistent inputs.

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 behavior: "Returns every datawebot tool available right now with its input schema, which need sign-in, and how to sign in." It clearly identifies this as the catalog/discovery endpoint and distinguishes it from run_tool for tools added later.

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?

It explicitly says "Start here" and gives the exact refresh condition: call again when meta.catalog_version differs from the one first seen. It also names run_tool as the path for tools added after session start, covering both when to use this tool and an alternative.

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