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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds useful context ('No generation or charge', the pinned-DNA prerequisite, and that existing storyboard rules still apply), but given destructiveHint=true it never clarifies what state is altered or whether the change is reversible.

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?

Three short sentences, front-loaded with the core action and no wasted words. The prerequisite and cost clarification are compactly stated.

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?

An output schema exists so return values need not be described, and annotations cover the mutation/safety hints. The description supplies the key prerequisite and cost non-impact, making it reasonably complete for a two-parameter toggle, though it leaves the state-change semantics unstated.

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 only 50% — projectId is documented but the artistPresence enum values are bare. The description partly compensates by explaining the meaning of 'featured' (requires pinned DNA) and names both enum values, but adds no detail on the projectId format or the downstream effect of each mode.

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 and resource ('Set featured or not_featured for this project'), which an agent can map directly onto the tool's effect on artist presence. It is clear, though it does not explicitly distinguish this tool from any sibling (there is no obvious competing presence-setter, but no differentiation is offered either).

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?

It implies usage and states a precondition ('Featured requires pinned DNA'), which guides the agent on when 'featured' is valid. However, it gives no explicit when-to-use vs. when-not-to-use guidance and names no alternative tool or workflow.

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