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

No annotations are supplied, so the description carries the full behavioral burden. The verb 'List' implies a safe read, but nothing is said about permission requirements, result ordering, pagination, or behavior when a profile has no schedules. The example clarifies data shape only, not behavior.

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?

A single front-loaded sentence with the resource scope first and a genuinely illustrative example second. No padding, no restated boilerplate.

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 single-parameter read tool with no output schema and no annotations, the description covers the core purpose but leaves the agent guessing about result format and scope of returned schedules. It is minimal but not misleading, which is the minimum-viable level.

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 100% for the single parameter (profile_id), including a pattern and a discovery hint, so the schema already does the work. The description adds nothing beyond what the schema states, which is the expected baseline for a fully documented single parameter.

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 names a specific verb and resource ('List time-based schedules on a profile') and the parenthetical example ('bedtime 21:00-07:00 on weekdays') makes the resource concept concrete and distinct from list_rules or list_devices. It stops short of explicitly naming a sibling or exclusion, so it is clear but not maximally differentiated.

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?

There is no when-to-use guidance, no mention of prerequisites, and no alternative named (e.g. create_schedule/delete_schedule for mutation). The only routing hint, 'use list_profiles to discover IDs', lives in the input schema rather than the description, so the description itself provides essentially no usage direction.

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