maltego_list_entities

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by detailing the return formats (markdown and JSON), pagination behavior (offset, limit, has_more, next_offset), and that it operates on the active graph. 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?

The description is concise with clear sections (Args, Returns) and front-loads the main purpose. Every sentence adds value without repetition. The structure is easy to parse for an AI agent.

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 tool has 5 parameters and an output schema, the description fully covers the input and output. It explains pagination, filtering, and both response formats. No missing information; the tool is complete for a list operation.

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?

Despite schema description coverage being 0%, the description thoroughly documents all parameters with additional context: type_filter (Maltego type), value_contains (case-insensitive substring), limit (range 1-500, default 50), offset, and response_format (enum with defaults). This adds significant meaning beyond the schema's property descriptions.

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 'List entities on the active graph' with specific verb and resource. It distinguishes from sibling tools like maltego_get_entity (single entity) and maltego_list_links by focusing on entities with optional filtering and pagination.

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 documents parameters and their defaults, making it clear how to use the tool. However, it does not explicitly state when not to use it or compare to alternatives like maltego_get_entity. The context is implied but not explicitly stated.

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