list_content

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

The description implies a read-only operation without annotations. It states the tool 'list' content, indicating non-destructive behavior. However, no additional behavioral traits (e.g., pagination, latency) are disclosed.

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?

A single sentence that is concise and front-loaded with the action and target. No redundant or extraneous information.

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 no parameters and an output schema expected (not shown), the description is mostly complete for a simple listing tool. It could mention that the output contains these three entity types, but the output schema likely covers that.

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?

No parameters exist, so schema coverage is 100%. The description adds value by specifying the entities listed (databases, projects, runs) and the 'currently hosted' context, which is sufficient for a param-free tool.

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 lists databases, projects, and runs on the Gigwa server. The verb 'List' and specific resources distinguish it from sibling tools like 'gigwa_server_info' which provides server info.

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 on when to use this tool versus alternatives. For example, 'gigwa_server_info' could be a sibling with overlapping purpose, but the description does not clarify when to choose one over the other.

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