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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds the access-scoping constraint (results belong only to this credential's profile), which is useful context beyond annotations. It does not describe pagination, rate limits, or return format, and with annotations carrying the behavioral burden, a 3 is appropriate.

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 sentences, front-loaded with the resource list, and the scoping constraint is placed second. Every clause adds information without waste.

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 the simplicity (no parameters, no output schema, annotations cover safety), the description is nearly complete: it says what is read, who sees it, and the access boundary. The only missing piece is explicit guidance on when to choose this over sibling read tools like account_overview, but that is a minor gap in this context.

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 tool has zero parameters, so there is nothing to document beyond what the schema already shows. The baseline for zero parameters is 4, as no additional parameter semantics are needed.

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 names a specific read verb and a concrete resource set: carousels, video covers, generation progress, and shared AI credit balance. It clearly states what is returned, distinguishing it from write siblings like studio_save or studio_export. It does not explicitly contrast with siblings such as studio_project or account_overview, but the scope is clear enough for an agent to identify the resource.

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 description implies usage by stating the results belong only to this credential's profile, which hints at the scoping condition. However, it does not say when to use this tool versus alternatives like account_overview or studio_project, leaving the agent to infer from the resource list.

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