Get OpenSora 2 resources

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds a meaningful behavioral boundary—'Does not fetch external content'—which tells the agent this is a local/canonical lookup rather than a web fetch. No contradiction with annotations.

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 that states the main purpose and then adds a critical constraint. There is no filler or redundant restatement of the tool name.

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 one optional parameter, rich annotations, and no output schema, the description is nearly complete for a simple lookup tool. It covers what is returned, the domain, and a key behavioral limitation; it only lacks more explicit guidance about when to invoke it relative to 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?

The schema has 0% description coverage, but the description compensates by listing the exact resource categories that map to the topic enum values (prompt, workflow, technical, safety). It does not explicitly name the 'topic' parameter or explain 'all', but the enum is simple and self-documenting.

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 specific verb ('Return') and names the exact resource set: canonical OpenSora2.com prompt, workflow, technical, and safety resources. This clearly distinguishes it from the sibling tools, which are about building prompts, planning shots, and diagnosing prompts.

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 when to use the tool: whenever an agent needs canonical OpenSora2 resources. However, it does not explicitly state when to prefer this tool over the siblings or provide exclusion conditions beyond the note that it does not fetch external content.

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