Get favorite people

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the meaningful detail that the tool switches to upcoming movies/episodes featuring the favorited people, but it says nothing about pagination behavior, response shape, or what happens with an empty favorites list.

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?

One sentence, front-loaded with the primary behavior and with the mode switch appended. The parenthetical is a bit dense but nothing is wasted.

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 3-param read-only tool with no output schema, the description conveys the two distinct return modes, which is the key thing an agent needs. Remaining gaps (pagination, response contents) are minor for a read-only list tool.

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 67%: offset and upcoming are documented in-schema, limit is not. The description usefully clarifies that the upcoming flag returns releases 'featuring them' rather than the favorites themselves, which goes beyond the schema's terse 'Return upcoming releases instead', but it leaves limit/offset semantics untouched.

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?

States a specific verb+resource ('get the user's favorited people') and names the alternate mode. It never distinguishes itself from the sibling mutations favorite_person/unfavorite_person or from get_person, so the sibling differentiation is only partial.

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 'upcoming=true' clause implies an alternate usage, but there is no guidance on when to call this versus get_person or favorite_person, and no mention of prerequisites such as authentication or a populated favorites list.

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