get_schedule

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

There are no annotations, so the description carries the full behavioral burden, and it discloses nothing: no auth/permission needs, no read-only confirmation, no return shape, and no notes about what the required identifiers must refer to.

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 single line is short, but it is under-specified rather than concise: it conveys no actionable content beyond the title, so brevity here is a defect, not a virtue.

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 tool with five required parameters, no annotations, and no output schema, the description is completely inadequate — an agent cannot determine what identifiers are valid or what it will receive back.

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?

Five required parameters (robot_sn, plan_uuid, year, month, day_of_month) have 0% schema description coverage, and the description explains none of them — not even the year/month/day semantics or whether they select a specific day's shift.

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 is essentially a bilingual restatement of the tool name, adding only the word 'details' (详情). It does not distinguish this tool from siblings like list_schedules, get_schedule_calendar, or update_schedule, leaving the agent to infer that this fetches one schedule's details.

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 when-to-use guidance is given: no mention of when to call get_schedule versus list_schedules or get_schedule_calendar, and no prerequisites. The agent must guess from the name alone.

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