algolia_list_indices

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

No annotations are present, so the description bears full responsibility. It states 'List all Algolia indices', implying a read-only operation, but does not disclose any behavioral traits such as pagination limits, authentication requirements, rate limits, or potential errors. This is insufficient for safe and effective use.

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 sentence of 6 words, front-loaded with the action word 'List'. Every word is essential, and there is no redundancy or filler. It is optimally concise.

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 list tool with no output schema, the description is minimally adequate. However, it lacks context about pagination, the meaning of 'the application', and what the output includes (e.g., index names, configuration). An agent might need more detail to use it effectively.

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 already provides descriptions for both parameters (app_id: 'Algolia Application ID', api_key: 'Algolia Admin API Key'), achieving 100% coverage. The description adds no additional meaning or context beyond the schema, warranting the baseline score of 3.

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 action (list), the resource (Algolia indices), and the scope (in the application). It distinguishes from sibling tools like algolia_search or algolia_browse_index by explicitly saying 'list all', which implies a retrieval of all indices rather than a search or browse.

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?

No guidance is provided on when to use this tool vs alternatives (e.g., algolia_search, algolia_browse_index). It does not mention prerequisites, scenarios, or exclusions, leaving the agent without context for optimal tool selection.

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