trawl_get_pool

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

No annotations are provided, so the description carries the full burden. The word "get" implies a read, but the description says nothing about what happens if no pool is loaded (error vs. empty result), whether the call has any side effects, or the shape of the response.

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 front-loaded sentence with no filler. It is efficiently sized, though the brevity reflects under-specification rather than tight editing.

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 output schema, no annotations, and no parameters, the description is the only source of information about behaviour — and it does not indicate what 'information' is returned or the failure mode when no pool is loaded. For a status-style tool this leaves a real gap.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies since no parameter semantics are needed.

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?

"Get information about the currently loaded pool" names a verb (get) and a resource (pool), and the qualifier "currently loaded" hints that it targets one specific pool rather than a collection. But "information" is opaque — it never says what data is returned, and it is not differentiated from near-neighbours like trawl_graph_stats, trawl_ingest_status, or trawl_list_pools.

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?

There is no when-to-use guidance, no mention of an alternative such as trawl_list_pools for enumerating pools, and no stated prerequisite that a pool must already be loaded via trawl_load_pool. The only usage hint is the phrase "currently loaded," which the agent must interpret itself.

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