get_fade_update_rate

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

No annotations are provided, so the description carries the burden and does so well: it explains what the setting controls, the CPU/smoothness tradeoff, the default, and typical operating values. It does not address permissions or failure modes, but for a zero-parameter read this is strong context beyond the structured fields.

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 with the core statement, then layered context and typical values with no filler sentences. The reference-value list is slightly beyond the minimum needed to invoke the tool, but it is scannable and each line adds practical meaning.

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?

With no output schema and no annotations, the description usefully documents the return contents (Hz value plus a default flag) and interpretation guidance. It stops short of covering error conditions or cross-referencing the setter sibling, but the essentials for a correct call are present.

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 tool takes no parameters, so the baseline is 4; there is nothing for the description to clarify and it correctly spends no space on parameters.

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 first sentence gives a precise verb+resource with a unit ('Get the current fade engine update rate in Hz'), which unambiguously identifies this as the read counterpart to the sibling set_fade_update_rate. An agent can distinguish it without opening any schema.

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?

Usage is only implied: the description explains what the rate means but never states when to check it (e.g., before tuning fade performance) or points to set_fade_update_rate as the mutation alternative. For a simple getter this is adequate but leaves routing to inference.

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