get-stats

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'get statistics' without specifying what statistics are returned, whether the operation is purely read-only, or whether it depends on a prior load action. This leaves significant ambiguity for an agent invoking the 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?

The description is a single, short sentence with no extraneous words. It is front-loaded and immediately conveys the tool's purpose, making it highly concise and well-structured.

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?

Given the low complexity and no output schema, the description is too vague to be considered complete. An agent cannot infer what 'statistics' will be returned (e.g., counts of components/stories, metadata about the loaded data) or how to interpret the result. More specifics would greatly improve completeness.

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 has zero parameters, so the baseline is 4. The description adds minimal but helpful context by clarifying that the statistics relate to 'loaded storybook data', which is not fully expressed in the empty schema. No parameter documentation is 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?

The verb 'Get' and the resource 'statistics about loaded storybook data' clearly describe a read-only tool for retrieving aggregate information. It is distinct from sibling tools like get-component or get-story, which focus on specific items rather than overall statistics, though it does not explicitly name those alternatives.

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 usage context is provided. There is no mention of when to use this tool (e.g., only after load-storybook) or how it differs from alternatives like searching or listing components. The word 'loaded' implies a prerequisite, but this is not stated explicitly.

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