trawl_graph_stats

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

With no annotations provided, the description carries the disclosure burden; 'Get' implies a non-destructive read, and it names the returned metrics, which is useful since there is no output schema. However, it says nothing about required permissions, cost, or what happens when a pool has no graph, which are meaningful gaps for an unannotated tool.

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 naming the resource first and the returned statistics parenthetically. No filler, though it could also have used the space for scoping or prerequisite 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?

For a simple one-parameter read tool with no output schema, listing the metric categories gives the agent a reasonable expectation of the return value. The remaining omission is the pool prerequisite, which is minor for this complexity level.

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 100% (one required parameter, pool_name), so the schema already carries the parameter documentation and baseline 3 applies. The description adds no extra meaning about the pool_name argument, such as whether it must be an existing indexed pool.

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?

Names a specific verb (get) and resource (knowledge graph statistics) and even enumerates what the stats cover (node/edge counts, entity types). It is clearly distinct from siblings like trawl_build_graph or trawl_graph_export, though it never says so explicitly.

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 statement of when to call this versus alternatives such as trawl_build_graph, trawl_graph_export, or trawl_get_pool, and no prerequisites (e.g., whether the pool must be built first). Usage is only inferable from the name and the word 'statistics'.

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