Bangumi TV MCP Service

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists related subjects but doesn't describe behavioral traits such as whether it's read-only, pagination behavior, rate limits, error handling, or authentication needs. The mention of 'Returns: Formatted list' hints at output structure but lacks detail, leaving significant gaps.

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 appropriately sized and front-loaded, with the core purpose stated first. The 'Args' and 'Returns' sections add structure, though they could be more concise. Every sentence contributes, but the formatting is slightly verbose for such a simple tool.

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 tool's moderate complexity (listing relations), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'related subjects' entail beyond examples (sequels, prequels, adaptations), how results are formatted, or error conditions. The agent lacks sufficient context to use the tool effectively without trial and error.

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 adds minimal semantics beyond the input schema. It specifies that 'subject_id' is 'The ID of the subject,' which is slightly more informative than the schema's 'Subject Id' title, but schema description coverage is 0%, and the description doesn't compensate by explaining format, constraints, or examples. With only one parameter, the baseline is 4, but the lack of additional context reduces this to 3.

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 clearly states the tool's purpose: 'List related subjects (sequels, prequels, adaptations) for a subject.' It specifies the verb ('list'), resource ('related subjects'), and scope ('for a subject'), distinguishing it from siblings like get_subject_details or search_subjects. However, it doesn't explicitly differentiate from get_subject_characters or get_subject_persons, which also list related entities for a subject.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like get_subject_characters or get_subject_persons, nor does it specify prerequisites, exclusions, or contextual triggers. The agent must infer usage based on the purpose alone.

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