get_crew_brief

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

readOnlyHint=true already tells the agent this is a safe read. The description adds that the returned brief enables role-play ('act as that role'), which is genuinely useful framing, but says nothing about brief contents, size, or whether the brief is static per role.

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?

Two short sentences, front-loaded with purpose before the enumeration. The role list is mildly redundant with the schema enum but short enough not to bloat the definition.

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 single-param read tool with readOnly annotations, most of what an agent needs is present. With no output schema, however, the description never indicates what a 'brief' actually contains or returns, leaving an agent to call blind.

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?

One required enum parameter. The description lists the exact role values, but that list is already fully enumerated in the schema, so it adds no syntax or selection guidance beyond the structured field. Baseline 3.

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 and resource ('Get one film-crew role's brief') plus the downstream purpose ('so you can act as that role'), which distinguishes it from siblings like studio_info or get_house_rules. Lacks only an explicit contrast with a named alternative.

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 clause 'so you can act as that role' implies the triggering situation, but there is no explicit when-to-use/when-not guidance and no reference to any of the 20 sibling tools. Usage must be inferred.

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