paragraph_count

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

No annotations are provided, and the description discloses only the cost ($0.001 USDC) without any behavioral details such as input requirements, output format, or side effects. It does not clarify how paragraphs are counted or what the agent should expect.

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?

While very short, it is under-specified rather than concise; it omits essential information about the tool's function and usage.

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?

The tool is a simple text-analysis function, but with no output schema, no parameter details, and no description beyond the name and cost, it is not usable by an agent. Overall inadequate for a 1-parameter tool.

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 input schema only contains a generic 'params' object with no specific properties, and the description adds no parameter semantics. The agent has no indication of what fields to provide (e.g., 'text' or 'paragraphs').

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 merely repeats the tool name ('paragraph count') and categorizes it as 'Other Utilities tool'. It does not state the operation, such as counting paragraphs in a provided text, nor distinguishes it from sibling text-analysis tools.

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 guidance on when to use this tool versus alternatives like word_count or char_count. The description only mentions category and cost, with no usage context or exclusions.

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