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

Annotations already declare readOnly, idempotent and non-destructive behavior. The description adds the pagination strategy (next cursor or since revision), which is useful behavioral context beyond the annotations. It does not explain ordering, history contents, or how totals are computed.

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?

Two short sentences with no wasted words, and the main operation is stated first. The terseness is appropriate, though it leans toward under-specification rather than completeness.

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 only two optional parameters, rich annotations, and an output schema, so return values need not be described. Still, with zero schema descriptions, the agent needs more detail about what 'since' and 'cursor' mean and what exactly the history contains. The current description is minimal but not wholly inadequate.

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 0%, so the description must carry the burden of explaining the two optional parameters. It partially does so by implying cursor is for pagination and since is a revision marker, but it does not define what a revision is, the cursor format, or when to prefer one mode over the other.

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 states a read operation over 'application history and submission totals', which gives a rough sense of the resource. However, it never clearly says this lists applications or how it differs from sibling get_application. The agent must infer that this is the collection-level counterpart to the singular getter.

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 sentence 'Use next cursor or since revision' describes parameter mechanics, not when to select this tool over get_application or other siblings. There is no explicit context for pagination versus incremental revision reads, nor any exclusions.

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