black_souls_get_variables

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds the constraint on the number of IDs per call, but does not disclose return format or behavior for invalid IDs. Since annotations cover the core behavioral traits, the description adds marginal value.

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 consists of two short sentences that immediately convey the purpose and a key constraint. Every word is necessary; no filler.

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 simplicity (one parameter, output schema exists, annotations rich), the description covers the essential purpose and constraint. It does not explain scenarios like missing IDs, but the output schema likely handles that. Overall complete enough for 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 description mentions 'by ID' and 'up to 64 IDs per call', providing some context for the single parameter 'ids'. However, with schema description coverage at 0%, the description could more explicitly explain that the parameter is an array of integers in the range 1-9999. It adds meaning but is not fully compensatory.

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 verb 'Read', the resource 'RPG Maker game variable values', and a key constraint 'by ID' and 'Request up to 64 IDs per call'. It distinguishes from siblings like black_souls_get_switches (which reads boolean switches) and black_souls_memory_read (which reads arbitrary memory).

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 for reading variable values by ID, and gives a constraint on the number of IDs per call. It does not explicitly state when to use this tool versus alternatives, but the naming context and sibling names provide sufficient differentiation.

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