get-logs-indexes

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

The description only states 'Get', implying a read-only operation, but with no annotations, it fails to disclose any behavioral details such as data freshness, permission requirements, or rate limits. The description does not add value beyond the verb.

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 that is concise and front-loaded with the key purpose. Every word contributes meaning without redundancy.

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 zero parameters and no output schema, the description is adequate for a simple retrieval tool. However, it does not mention pagination, sorting, or any constraints, leaving room for improvement in completeness for an agent unfamiliar with the API.

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?

There are no parameters, so the schema coverage is 100% vacuously. The description adds meaning by specifying that the tool returns configurations including retention and exclusion filters, helping the agent understand the content of the response. This meets the baseline 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 'Get log index configurations including retention and exclusion filters', specifying the verb, resource, and what the configurations include. It distinguishes from similar sibling tools like 'get-log-indexes' by adding detail about retention and exclusion filters, but does not explicitly differentiate them.

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 versus alternatives like 'get-log-indexes' or other log-related tools. The agent has no context for selection.

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