Show A Crew

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

Annotations already provide readOnlyHint=true and idempotentHint=true; description adds minimal behavioral context beyond stating it returns a JSON object. No mention of authentication or rate limits, but annotations cover safety profile.

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?

Description is 4 sentences, front-loaded with purpose. Some redundancy (e.g., 'returns a JSON object') but overall efficient. API endpoint info is extra but not harmful.

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 read-only show operation with good annotations, the description adequately covers essential information. No output schema is present, but the description mentions return type. Slightly lacking in explaining what fields the JSON object contains, but acceptable for a straightforward 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?

Input schema has 100% coverage with descriptions for all parameters. Description redundantly lists required parameters (project_id, id) but adds no new meaning beyond 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?

Clearly states 'Return Crew detailed information' and specifies that it fetches full details of a specific Directory record by identifier. Distinguishes from list tools (e.g., list_all_project_crews) by requiring unique identifier.

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?

Explicitly says 'Use this to fetch the full details of a specific Directory records by its identifier', indicating when to use. Does not explicitly exclude listing or mention alternative tools, but context suggests it for single record retrieval.

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