get_languages

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds project-scope context ('configured in your SimpleLocalize project') but does not disclose return format or pagination; this is acceptable given the simple list nature and annotation coverage.

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 compact: two sentences plus a bullet point, with the core function front-loaded. Every sentence earns its place by stating what the tool does and why to use it, with no redundant fluff.

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 parameterless read-only list tool with no output schema, the description is mostly complete: it names the resource, scope, and use case. It could theoretically mention the shape of the returned language list, but 'list all languages' sufficiently implies the outcome for an agent.

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 input schema is empty and schema coverage is 100%, so the description does not need to explain parameters. The explicit statement 'No parameters required' reinforces the schema and is useful for an agent; baseline 4 applies for zero-parameter tools.

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 'will list all languages configured in your SimpleLocalize project', identifying a specific action and resource. The use case 'to see available languages for translations' further clarifies its role and distinguishes it from singular operations like get_language.

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 provides clear context for when to use the tool: to see available languages for translations. It does not explicitly mention when not to use it or name alternatives, but for a parameterless list operation the usage guidance is sufficient.

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