si_stats

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

With no annotations provided, the description carries the full burden. It usefully discloses the auth requirement and that counts cover only CC0-licensed content, but says nothing about whether the call is read-only (implied), rate limits, or whether counts are collection-wide or scoped. The output schema presumably covers the return shape.

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?

Two short sentences, front-loaded with the result the tool produces and followed by the auth prerequisite. Nothing is wasted.

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?

An output schema exists, so return values need not be described, and the description covers the resource scope and the auth requirement. It could say more about whether the stats are global or filterable, but for a zero-parameter counter it is nearly complete.

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 the baseline is 4 — there are no argument semantics left for the description to explain. Schema coverage is reported at 100%.

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?

States a specific resource (CC0 objects and media counts) with the implied verb 'counts', and the 'CC0' scoping makes it distinguishable from the search/fetch siblings. It does not explicitly name an alternative, but no sibling does anything similar, so confusion risk is low.

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?

The description gives a prerequisite ('Needs SMITHSONIAN_API_KEY') but no explicit when-to-use or when-not-to-use guidance. Usage is implied by the purpose — call it to get aggregate collection counts — but there is no routing or exclusion language.

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