person_schedule

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

Discloses the combination of two APIs and parameter mapping (person_id used for both Forecast and Harvest lookup). However, with no annotations provided, it lacks detail on read-only nature, error handling, or permissions. No contradiction with annotations.

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?

Concise description: two sentences for purpose followed by parameter explanations. Front-loaded with purpose. No wasted words, though slightly more detail could be added without bloat.

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?

Covers core functionality and parameter details. With output schema present, return values need not be described. However, missing context on edge cases (e.g., missing harvest_user_id) and error scenarios.

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?

All three parameters are explained: person_id's dual role, and the YYYY-MM-DD date format for start_date and end_date. Since schema coverage is 0%, this adds essential meaning beyond the schema names.

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?

Clearly states the tool retrieves a person's complete schedule combining Forecast assignments and Harvest time entries. Distinguishes from siblings by emphasizing the combination of two data sources.

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?

Implies usage for viewing both scheduled and logged work, but does not explicitly state when to use this versus alternatives like list_assignments or list_time_entries, nor provide when-not-to-use guidance.

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