List Entries

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

No annotations provided, so description carries full burden. It discloses that the tool returns metadata only ('no payload'), supports pagination with a max limit of 200, and notes that unlinked entries lack moduleName. Does not explicitly state it is read-only, but 'returns' implies a safe operation.

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?

Three compact sentences. First sentence states the main purpose and return fields. Second adds filter and pagination details. Third provides additional context about unlinked entries and a sibling alternative. No unnecessary words.

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 7 parameters and no annotations, the description covers the return shape, filters, pagination, and a sibling note. It does not explicitly mention the query, offset, or projectId parameters, but these are documented in the schema. For a listing tool with many siblings, it provides sufficient context to guide usage.

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% with good descriptions for each parameter. The description adds value by summarizing supported filters (kind, moduleName, tags) and pagination limit (max 200), and provides context about unlinked entries and moduleName. This supplements the schema without duplicating.

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 returns the entry catalog with specific fields (id, kind, title, tags, moduleName) and explicitly mentions 'no payload'. It distinguishes from the sibling 'get-slice' by directing to that tool for typed horizontal views.

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?

Provides context for when to use validate ('run validate after edits') and contrasts with get-slice for typed horizontal views. Does not mention other siblings like search-entries or get-entry, but the guidance given is clear and useful.

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