get_ik_solver_settings

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

Although annotations already cover readOnly/idempotent/non-destructive, the description adds genuinely useful behavioral context: the serialization scheme differs by solver type (curated snake_case keys for FullBodyIK vs. generic camelCase struct dump for Limb/Pole/BodyMover/etc.). That shape-of-return behavior is not derivable from the 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?

Front-loaded purpose followed by the solver-type serialization caveat and a compact return-shape block. Dense but every sentence (especially the solver-type serialization distinction) earns its place.

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?

There is no formal output schema, but the description compensates with an inline 'Returns: { ... }' shape and explains the settings object's variability by solver type. Combined with annotations that define the safety profile, this is largely complete for a read tool.

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?

Schema description coverage is 100%, so ik_rig_path and solver_index are already documented. The description echoes the notion of 'solver-level parameters for the specified solver' but adds no new syntax or indexing detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Get') and resource ('solver-specific settings for a solver in an IK Rig') and scopes it to solver-level parameters. However it does not distinguish itself from closely-named siblings like get_ik_solver_details, get_ik_bone_settings, or get_ik_rig_info, leaving overlap for the agent to resolve.

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?

There is no explicit when-to-use guidance, no when-not-to-use, and no mention of the obvious alternative/companion set_ik_solver_settings or get_ik_solver_details. The agent must infer the right entry point from naming alone.

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