speaker-set

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only notes that the property is 'writable', implying mutation, but it does not explain what happens if the property is read-only, whether the speaker must exist, or any potential side effects. There is also no mention of error handling or return behavior.

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 a single, concise sentence with no wasted words. However, it is under-specified for a mutating tool with three parameters and no annotations, so while it is compact, it lacks necessary detail. The conciseness itself is appropriate, but it does not earn its place fully because it omits critical information that could be added without bloat.

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 no annotations, no output schema, and 0% parameter coverage, the description is severely incomplete. It provides minimal context about the tool's scope, behavior, or parameter semantics, leaving the agent to rely solely on the schema. For a mutation tool, this is highly inadequate, as the agent needs to know prerequisites, side effects, and parameter constraints.

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 schema has three parameters (name, property, value), and schema description coverage is 0%. The description does not elaborate on any of these parameters, merely repeating the words 'property' and 'value' without adding meaning. The schema titles provide some basic context, but the description adds no value beyond what the schema already conveys, and it fails to compensate for the 0% 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 action (set) and the resource (a speaker data-block), and it is specific about setting a single writable RNA property. It distinguishes from sibling tools like speaker-create, speaker-list, and speaker-report, which handle creation, listing, and reporting rather than property modification.

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 guidance is provided regarding when to use this tool versus alternatives. There is no mention of prerequisites (e.g., speaker must exist), no indication that this is for modifying existing speakers as opposed to creating them, and no reference to other tools like speaker-report for querying properties.

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