vrc_dynamics_budget

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

No annotations provided, so the description must fully disclose behavior. It states 'Calculate' and 'Checks' but does not explicitly confirm whether the tool is read-only, destructive, or has side effects. Lack of permission or safety context is a gap.

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, front-loaded with the purpose, and includes structured parameter examples without unnecessary text. Every sentence adds value.

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?

The tool has an output schema (not shown) which likely documents return values, so the description is adequate. It covers the key function and parameter formats, but could mention that it is non-destructive or provide context on when to use it in a pipeline with other 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 input schema defines all parameters as strings but the description provides detailed JSON format examples (arrays with specific fields). This adds essential structure beyond the schema, especially with 0% schema description 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 calculates VRChat Avatar Dynamics budget usage, checking PhysBones, Contacts, and Constraints against performance rank limits. This is specific and distinct from sibling tools like vrc_validate, which has a broader scope.

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?

No explicit guidance on when to use this tool versus alternatives. The description does not specify prerequisites, when to avoid, or contrast with similar tools like vrc_physbone_config or vrc_validate.

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