togoid_countId

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

Discloses it is lightweight, single-hop, pairwise, and does not return mapped IDs. No annotations present, so description covers safety adequately. Minor omission on error or edge cases, but overall strong.

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?

Concise and well-structured: main purpose upfront, bullet points for use cases, then technical detail. No superfluous sentences.

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 output schema exists and 3 params fully described in schema, the description provides complete context: purpose, usage, parameter nuances, and comparison with sibling 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?

Schema coverage is 100%, baseline 3. Description adds value by explaining the different parameter format for source/target vs convertId's route, and clarifies ids accepts list or comma-separated string.

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?

Description clearly states it counts convertible IDs as a pre-check before bulk conversion. Specifies 'source' and 'target' as separate args, distinguishing it from convertId.

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 lists three use cases (verify format, estimate size, check route) and contrasts with convertId, providing when-to-use and when-not-to-use guidance.

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