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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about pagination and filtering, which is useful but does not disclose additional behavioral traits such as response size, rate limits, or prerequisites. Given the annotation coverage, this is adequate but not exceptional.

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, front-loaded sentence: 'List all report schedules in the workspace with pagination and active status filtering.' Every word contributes to the core function, scope, and key capabilities. No unnecessary filler or repetition.

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 simple list tool with strong annotations (readOnlyHint, idempotentHint, destructiveHint), the description covers the essential: what is listed, where, and available options. It lacks details about the return format or edge cases (e.g., empty results), but for a read-only list operation, this is sufficient. A score of 4 reflects completeness for the tool's complexity.

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 only 29% (query and workspace_id have descriptions). The description compensates by mentioning 'pagination' (which maps to limit, cursor, offset) and 'active status filtering' (active parameter), adding meaning beyond the raw schema. However, it does not explain brand_id or the exact mechanics of pagination parameters, so it is not a perfect score.

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 the specific verb 'list' followed by the resource 'report schedules' and scope 'in the workspace', clearly distinguishing it from sibling tools like create_report_schedule, get_report_schedule, and delete_report_schedule. It also mentions pagination and active status filtering, adding specificity beyond a generic list operation.

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 provides clear context: this tool lists all report schedules in the workspace, with optional pagination and filtering. It does not explicitly state alternatives or when-not-to-use scenarios, but the purpose is obvious from the name and description, so it earns a 4 rather than a 3.

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