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

Annotations already declare readOnlyHint=true. The description adds value by stating the portal link is not returned and explaining role ordering per post, providing behavioral detail beyond the annotation.

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 few sentences with no fluff; it front-loads the purpose, then explains roles, usage, and caveats in a logical order. Slightly long but every sentence earns its place.

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?

Given no output schema, it implies the return includes member_id and name (via 'use the returned member_id or name') and explicitly states what is not returned. It's complete for a simple list operation with one optional parameter.

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 100% with a property description, but the tool description enriches the role enum by defining each role's function (creator films, editor edits, clipper cuts clips, poster publishes), adding meaning beyond the schema.

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 clearly states the tool lists production crew (editors, clippers, posters) with specific roles and their per-post ordering. It's a specific verb+resource that distinguishes it from other list_* tools.

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?

It explicitly instructs to use the returned member_id/name with assign_crew, and notes the private portal link is not returned here, directing to create_crew_member or the app. This gives clear when-to-use and what-not-to-expect context.

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