get_assignment_detail

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

There are no annotations, so the description carries the full burden for behavioral disclosure. 'Return' conveys a read operation, and the mention of 'run and event timeline' adds some behavioral context about the response composition. However, it does not disclose not-found behavior, permissions, pagination, or any error-related caveats.

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 single front-loaded sentence with no wasted words. Every part of it conveys meaningful information about the resource and what is included in the result.

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 getter with one parameter and an output schema available, the description is minimally adequate: it names the resource and the main related entities returned. Yet it lacks guidance on when to choose this over sibling detail tools, and with no annotations it does not fully cover behavioral expectations.

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 description coverage is 0%, and the description does not explain assignment_id beyond the parameter's own name and title. The description's mention of 'assignment' creates a loose link, but it adds no format, source, or usage semantics for the sole required parameter.

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 uses a clear verb ('Return') and names a specific resource ('an assignment') with its composed contents ('run and event timeline'). This is enough to understand what the tool does, and the composition narrows it versus get_run_detail or get_workspace_detail, though it does not explicitly name sibling alternatives.

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?

No guidance is given about when to use this tool versus sibling detail getters such as get_run_detail, get_workspace_detail, or get_contract_detail. The tool's purpose implies use when an assignment's full detail is needed, but no context, exclusions, or preferred alternatives are stated.

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