firestarter_update_market

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the write nature is expected. The description adds key behavioral details: ownership requirement, clearing semantics, and that only specified fields are changed. No contradiction with 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?

The description is efficient, leading with the core purpose and then specifics. It is slightly long but every sentence contributes (ownership, fields, clear behavior, alternatives). No fluff.

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?

For a tool with 4 params, full schema coverage, and annotations, the description covers ownership, field selection, clearing, and routing to siblings. The one minor gap is that it doesn't explicitly state that fields not passed remain unchanged (though 'pass at least one' implies it). Overall, complete enough for correct invocation.

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 coverage is 100%, so each parameter is documented in the schema. The description adds semantic value beyond the schema by clarifying that empty strings clear fields and that at least one field must be provided, which enhances understanding of the 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 description states a specific verb ('update'), resource ('community market you own'), and the exact fields (display_name, tagline, discoverable). It distinguishes from siblings by naming firestarter_set_market_handle and firestarter_set_market_picks as alternatives for handle and picks. No ambiguity.

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?

Explicitly says to pass at least one field, clarifies when to clear fields with empty strings, and identifies sibling tools for other use cases (handle and picks). This is direct, actionable guidance with no ambiguity.

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