sap_fetch_epoch_page

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

The description only says 'Fetch', which implies a read operation, but provides no additional behavioral context. With no annotations, the description should disclose what happens if the page is missing, any side effects, or the nature of the returned data. It lacks depth 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, direct sentence with no redundant information. It perfectly balances brevity and clarity, earning the highest score.

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?

The tool has no output schema, so the description should compensate by explaining what an epoch page contains or how to use the result. The description is too sparse for a fetch operation, leaving the agent uncertain about the response format or purpose.

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?

Schema coverage is 100%, and the description restates the parameter semantics without adding extra meaning. The baseline score of 3 is appropriate since the schema already documents the parameters adequately.

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 ('fetch') and the resource ('epoch page'), with explicit inputs (session PDA, epoch index). It is distinct from sibling tools that fetch other resources like attestations or sessions, though no explicit differentiation is provided.

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 implies when to use the tool (to retrieve an epoch page), but does not provide explicit context, exclusions, or alternatives. No guidance on scenarios like missing data or prerequisites.

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