scheduled_instructions_search

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

There are no annotations, so the description bears the full burden of behavioral disclosure. It only says 'filter/sort/pagination' and does not clarify read-only behavior, return format, pagination defaults, filtering fields, or any side effects. It provides minimal added value beyond the tool name.

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 concise sentence, front-loaded with the action and resource. It contains no filler, though it is so brief that it sacrifices semantic richness for brevity.

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 search tool with no annotations, no output schema, sparse parameter definitions, and several closely related sibling tools, the description is incomplete. It omits return structure, pagination semantics, filter capabilities, and any usage context needed to select this tool correctly.

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 description coverage is 0%, so the description must compensate, but it does not explain the meaning of 'sort', 'start', or 'pageSize' beyond the broad phrase 'filter/sort/pagination.' The word 'filter' appears even though no filter parameter exists in the schema, which adds ambiguity.

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 a specific verb ('Search') and resource ('Scheduled Instructions'), and mentions filter/sort/pagination, which distinguishes it from related tools like scheduled_instructions_get_by_id or scheduled_instructions_create. It does not explicitly name sibling search tools like instructions_search or persistent_instructions_search, but the resource name is sufficiently specific.

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 about when to use this tool versus alternatives such as scheduled_instructions_get_by_id, persistent_instructions_search, or instructions_search. The intended usage is only implied by the verb and resource name.

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