ping

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

No annotations are provided, so the description carries full burden. It clearly discloses the tool's purpose (connectivity check), the expected condition (IDA plugin running and reachable), and the output ('Connected'). This is comprehensive for a simple read-only tool with no side effects.

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?

Two sentences conveying purpose, condition, and expected outcome. Every sentence adds value with no redundancy or filler.

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 zero parameters, no annotations, and a simple purpose, the description fully covers what an AI agent needs to know to use this tool correctly. The output schema exists, so return value details are already provided structurally.

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 and schema description coverage is 100%. The description adds no parameter details, which is acceptable as there are none to describe. The value is in explaining the return value, which goes beyond the schema.

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 tool checks connectivity to IDA Pro and specifies the success return value. It uses a specific verb and resource that distinguishes it from siblings, which are all about disassembly, analysis, and debugging.

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 implies this is a connectivity test, useful before calling other IDA tools. It does not explicitly state when not to use it or mention alternative tools, but given its unique purpose among siblings (no other tool checks connectivity), explicit exclusion is less necessary.

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