whodb_platform_transform

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds that workspace targeting is per-call and does not change defaults, which is mild behavioral context, but that same fact is already stated in the workspace schema description, so the net addition is limited.

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?

Three compact sentences that lead with the core action before the fields and workspace notes. Minor redundancy with the workspace schema text but no filler.

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 read-only single-resource inspection with full schema coverage, the definition is workable. It does not say what the inspection returns or how transform runs/build state relate to it, and with no output schema the description carries that burden, leaving a gap against the richer sibling tools.

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 100%, so the baseline is 3. The description reinforces the intent of the fields parameter and the workspace target, but adds no syntax, format or naming detail beyond what the schema already documents for id, fields and the nested workspace object.

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 ('Inspect one transform') plus scope ('in the selected hosted project'), which cleanly separates it from the plural whodb_platform_transforms list tool. It never names that sibling explicitly, so the differentiation is inferable rather than stated.

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?

'Inspect one transform' implies the single-resource read case, and the fields guidance implies iterative retrieval, but there is no explicit when-to-use vs. whodb_platform_transforms, transform_preview, transform_runs or transform_wait. Usage is only implied by the singular resource scope.

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