maltego_suggest_next_steps

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

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive hint. The description adds behavioral details: deterministic, prioritization of most-connected entities, and flagging of unavailable transforms. No contradictions.

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?

Well-structured with clear sections and front-loaded key message. Somewhat verbose with legacy note and rationale, but each sentence adds value. Could be slightly tighter but overall efficient.

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?

For a simple tool with one parameter and an output schema (mentioned but not shown), the description covers purpose, usage, behavioral traits, and parameter details adequately. No gaps remain.

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 repeats parameter info already present in schema (limit, response_format with defaults). Schema has high coverage (properties have descriptions), so baseline is 3. Description adds minimal new meaning beyond restating schema details.

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 it is a 'legacy simple heuristic for next transforms' and specifies what it does: deterministically recommends transforms, prioritizing most-connected entities. It explicitly distinguishes from sibling tool maltego_next_best_actions by calling that the preferred alternative.

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 explicitly advises to 'prefer maltego_next_best_actions' for real recommendations and states that this tool is for basic heuristic lists. It provides clear when-to-use and alternatives guidance.

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