get_subject_characters

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 mentions that the tool returns a 'Formatted list of related characters or an error message,' which gives some insight into output behavior. However, it lacks details on permissions, rate limits, pagination, or error conditions, which are critical for a read operation with no annotation coverage.

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 concise and well-structured, using clear sections for 'Args' and 'Returns.' It avoids unnecessary details and gets straight to the point. However, the 'Returns' section could be more specific about the format, slightly reducing efficiency.

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 complexity of having no annotations, no output schema, and low schema description coverage, the description is incomplete. It covers basic purpose and parameters but misses behavioral traits, error handling, and differentiation from siblings. For a tool in this context, more detail is needed to ensure reliable agent use.

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 explains that 'subject_id' is 'The ID of the subject,' which clarifies the parameter's purpose but doesn't provide format examples, constraints, or context. With 0% schema description coverage, this partial compensation is adequate but not comprehensive, meeting the baseline for moderate schema coverage.

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 characters related to a subject.' It specifies the verb ('List') and resource ('characters related to a subject'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_character_subjects' or 'get_subject_persons,' which prevents a perfect score.

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. With multiple sibling tools like 'get_subject_details,' 'get_subject_persons,' and 'search_characters,' there's no indication of context, prerequisites, or exclusions. This lack of guidance could lead to confusion in tool selection.

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