List All Project Crews

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds behavioral context: it returns a paginated JSON array, includes pagination metadata, and mentions the specific API endpoint. 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?

The description is 4 sentences: first states purpose, second gives usage, third describes return and pagination, fourth lists required params and API endpoint. Front-loaded and every sentence provides unique value.

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 list tool with clear annotations and full schema coverage, the description is complete. It explains return type, pagination behavior, required parameters, and API endpoint. No output schema needed as return is sufficiently described.

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 each parameter well-described. The description adds that project_id is required and that page/per_page control pagination, but this adds minimal value beyond the schema. Baseline 3 is appropriate as the schema does most of the work.

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 'Return a list of all Crews with details for a specified Project' with a specific verb and resource. It distinguishes from sibling tools like 'list_all_project_crew_ids' (which returns only IDs) and create/update/delete tools by emphasizing paginated overview with full 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?

The description explicitly says 'Use this to enumerate Directory records when you need a paginated overview, to find IDs, or to filter by query parameters.' This provides clear usage context. However, it does not mention when not to use or explicitly reference alternative tools like 'list_all_project_crew_ids' for just IDs, which would upgrade to a 5.

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