ispw_get_assignment

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context by naming the returned fields and noting that failures return an error message, though it does not discuss permissions or rate limits.

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?

It is front-loaded with the purpose and returned details, followed by standard Args/Returns/Examples sections. Some Args content repeats the schema, but the overall structure is efficient and readable.

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 rich annotations and an output schema, the description is largely complete for a simple getter. The main remaining gap is that it does not tell an agent how to obtain the required assignment_id when it is unknown.

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?

The description lists srid, assignment_id, and response_format with brief meanings plus one example. However, with low schema description coverage, it only partially compensates: it does not explain assignment_id format constraints or how callers should discover an assignment_id.

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 states a specific verb and resource: get detailed information about a specific ISPW assignment. It distinguishes a single-assignment retrieval from list-style siblings by emphasizing 'specific', though it does not explicitly name ispw_list_assignments as the discovery 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?

Usage is implied by 'specific ISPW assignment' and the example call, but there is no explicit when-to-use guidance, no when-not conditions, and no mention of using ispw_list_assignments to find an assignment_id. It is adequate but leaves routing to inference.

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