census

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

No annotations are provided, so the description carries the full behavioral burden. It implies a live read-only snapshot, but does not disclose whether it hits the network, rate limits, caching behavior, or what happens with empty venue lists. For a tool with no annotation coverage, this is a significant gap.

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 front-loaded sentence with no wasted words. However, the brevity may be excessive given the tool's three parameters and required enum, though structurally it is efficient.

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 and no annotations, the description should do more to explain the return shape, asset-class behavior, and parameter effects. It names the data categories but omits how to invoke the tool correctly across its required 'asset_class' enum.

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 only 33%, and the description does not explain the required 'asset_class' enum or how 'venues' and 'coin_pages' affect the snapshot. It vaguely maps 'coin universe' to coin_pages, but does not compensate for the undocumented parameters.

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 concrete resource and scope: a live whole-market snapshot covering venue market counts, coin universe, and DeFi TVL. This is clearer than the opaque name 'census', but it does not distinguish the tool from overlapping siblings such as 'universe', 'markets', or 'inventory_snapshot'.

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 guidance on when to use this tool versus alternatives like 'universe', 'markets', or 'inventory_snapshot'. No prerequisites, exclusions, or selection criteria are given, leaving the agent to infer usage from the name and one-line description.

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