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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds that it requires project context, a behavioral prerequisite, and clarifies it does not create/change/run schedules, implying no side effects. This adds value beyond annotations, though it omits details on return format or errors.

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?

Three sentences, front-loaded with the core purpose, then usage alternatives, then the context requirement. No fluff; every sentence contributes essential information.

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 schema already documents skip/take with defaults and max, and the description covers both list-all and single-schedule modes, the alternative tool, and the context requirement. It mentions returned fields (cron, timezone, next run time) but doesn't describe the full output shape or pagination details, though pagination is in the schema. Overall adequate for an agent to call 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 coverage is 100%, so baseline is 3. The description adds the relationship between scheduleId and testSuiteId – that scheduleId makes testSuiteId unnecessary – which is not present in the schema's individual parameter descriptions. This clarifies mutual exclusivity and enriches parameter understanding.

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 lists schedules of a test suite with specific fields (cron expression, timezone, next run time). It distinguishes itself from manage_test_schedule, which handles creation, changes, or runs, making the purpose unambiguous and distinct from siblings.

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?

Explicitly instructs when to use this tool versus alternatives: 'Use this to browse schedules; to create, change or run one use manage_test_schedule.' It also explains the scheduleId alternative, providing clear context for selecting the appropriate invocation mode.

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