list_translations

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

With no annotations, the description carries the burden. It explicitly states 'Read-only,' which is a key safety behavior, and describes the shape of each translation entry. It does not cover pagination, sorting, or error behavior, but for a simple listing tool this is adequate.

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 a single concise sentence that includes the output fields and the read-only flag. Every element is informative, with no redundant phrasing 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 the low complexity (2 parameters, no output schema), the description provides the purpose, output structure, and optional filtering while noting read-only behavior. It omits sessionId semantics and pagination details, but these are less critical for a list operation with simple parameters.

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 adds context for the culture parameter by noting 'for every culture or one,' while the schema already provides an example. The sessionId parameter is required but not described in either the description or schema, so the description only partially compensates for the 50% schema coverage.

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 uses the specific verb 'List' and resource 'object translations,' and enumerates the fields returned: culture, objectType, objectName, table, property, value. It clearly distinguishes from sibling list tools like list_cultures or list_roles by focusing on translations and supports filtering by a single culture.

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 context is clear: this tool lists translations, optionally filtered by one culture, and is read-only. However, it does not explicitly mention when to prefer this over alternatives like set_translation or delete_translation, nor does it state exclusions or prerequisites.

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