get_index

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

With no annotations, the description carries the burden. It discloses that the tool is a poll target and that it requires no wallet or API key, which addresses authentication and suggests a lightweight read operation. It lacks details on rate limits or error handling, but for a simple read-only endpoint this is acceptable.

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 two sentences long, front-loaded with the core action, and every phrase adds value. It avoids redundancy and conveys purpose, usage, and access requirements efficiently.

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's low complexity (no parameters, no output schema), the description covers the essential aspects: what it returns, when to use it, and that it's free. A minor gap is not naming the specific fetching tool to use after detecting a new digest, but the description is otherwise complete.

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 zero parameters and no input schema properties, so schema coverage is complete. The description adds context about the returned fields (master digest id, updatedAt, nextExpected time) and their purpose, enhancing understanding beyond the empty schema.

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 returns the current master digest id, updatedAt, and nextExpected time, using the specific verb 'poll target'. This distinguishes it from sibling tools like get_brief or get_latest, which likely serve different content-retrieval purposes.

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?

It explicitly advises 'Use it to detect a new digest before fetching,' giving clear when-to-use context. It does not mention alternatives or when-not-to-use, but the provided use case is actionable and sufficient.

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