Studio Status

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

No annotations are provided, so the description bears the full burden of disclosing behavior. It mentions a read-like status operation and a mutating rename operation, but does not explain side effects, permission needs, or the additional list_types action exposed in the schema.

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 sentence with no filler or repetition. It front-loads the primary status-checking purpose and keeps the alternative behavior brief, though it omits list_types for brevity.

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?

The output schema and full parameter schema reduce the burden on the description. However, the tool has multiple modes and several sibling tools, so a minimally viable description should at least mention all actions and hint at when rename is appropriate. This one leaves those gaps.

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 schema already documents all parameters. The description adds little semantic value beyond naming the status/rename actions, which is acceptable but not exceptional.

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 specific behavior: checking studio content generation status and getting URLs, or renaming an artifact. This distinguishes it from create/delete studio tools, though the additional 'rename' behavior is not clearly positioned relative to sibling studio_revise, and the list_types action is omitted.

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?

There is no guidance on when to use this tool versus alternatives such as studio_revise or research_status. The rename capability could easily be confused with studio_revise, and the description does not clarify when each should be preferred.

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