Estimate token counts for one or many skills, choosing body or description mode to measure content size.
Estimate tokens for one/many/all skills (mode: body|description).
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | ||
| name | No | ||
| names | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description does not disclose side effects, read-only nature, performance implications, or any behavioral details beyond the core function. The tool's behavior is largely unspecified.
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 unnecessary words. It efficiently conveys the primary action and mode options.
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 lack of annotations and output schema, the description is incomplete. It does not explain the return format, whether the estimate is per skill or aggregate, or any error conditions, leaving an agent uncertain about the outcome.
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 description partially clarifies parameters by indicating 'one/many/all' for name/names and 'mode: body|description', adding value over the bare schema. However, it does not define the exact meaning of each mode, how to specify 'all', or the relationship between name and names.
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 clearly states the action ('Estimate tokens') and the resource ('skills'), with a mode parameter indicating body or description. This distinguishes it from sibling tools like list_skills or bind_skills.
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 provides no guidance on when to use this tool versus alternatives. It does not mention conditions such as needing token counts before binding or when to choose a specific mode.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.