approvals_get_pending_scheduled_instructions

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

There are no annotations, so the description carries the full transparency burden. 'Returns' implies a read-only operation and the caller-scoping is disclosed, but pagination, ordering, empty-result behavior, and any authentication nuances are not covered. This is adequate for a simple zero-parameter read tool, though not thorough.

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 with no filler. The key qualifiers—'Scheduled Instructions', 'pending approval', and 'calling user can approve'—are front-loaded and every word earns its place.

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 zero-parameter, no-output-schema listing tool, the description supplies the essential selection and authorization filters. The exact return shape is not documented, but the intended result set is clearly defined, which is sufficient for an agent to decide whether to call it.

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 tool accepts zero parameters, so there is no parameter semantics burden for the description to carry. Schema description coverage is trivially 100%, and the zero-parameter baseline applies.

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 uses a specific verb ('Returns') and identifies the exact resource and scope: Scheduled Instructions that are pending approval and approvable by the calling user. This clearly separates it from sibling tools like approvals_get_pending_instructions and approvals_get_pending_persistent_instructions.

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 makes the usage context clear: use this tool to retrieve the scheduled-instruction approval queue for the current user. It does not explicitly name alternatives or state when not to use it, but the resource type and caller-scoping are specific enough to guide selection.

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