estimate_cost

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

The description explicitly states it 'Does not call Claude or modify anything — safe to run at any time', which is critical behavioral information. Since no annotations are provided, this fulfills the transparency burden.

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 compact with three sentences, no redundancy, and the main purpose is front-loaded. Every sentence adds value.

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 simple input (one required parameter) and the presence of an output schema, the description sufficiently covers the purpose and usage. No additional details are needed.

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 single parameter 'repo_path' has no description in the input schema (0% coverage). The description does not clarify format or expected values, leaving the agent to infer from the tool name. More detail would improve usability.

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 verb 'Estimate' and the resource 'Claude CLI calls ingesting a repo'. It distinguishes from the sibling tool 'ingest_repo' by specifying it is a preliminary estimation step.

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?

Explicitly advises to 'Use this BEFORE running ingest_repo on a large codebase', and explains what it reports and that it is safe to run at any time, providing clear guidance on when to use.

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