Toggle Featured Status

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

No annotations are provided, so the description should carry the disclosure burden. It states 'Toggle' implying it flips the current status, but does not disclose side effects, reversibility, permissions beyond 'Admin', or what happens when toggling an already featured item. Minimal behavioral insight.

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 two sentences: first states the action, second provides marketplace context and admin note. Extremely concise with no wasted words, and front-loaded with key information.

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 simple toggle with one required param and no output schema, the description provides the core purpose and admin scope. However, it lacks details on possible errors, the return value, or prerequisites beyond admin, leaving minor gaps.

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 input schema has 100% coverage with one parameter 'id' already described as 'The unique identifier of the pool item'. The description adds no additional meaning beyond that, just restates the purpose. Baseline 3 is appropriate as schema does the heavy lifting.

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 verb 'Toggle' and the resource 'featured status of a pool item'. It distinguishes from siblings by being the only toggle for featured status among many neuron_* tools, and adds context about appearing prominently in the marketplace and being an admin operation.

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?

The description mentions '(Admin operation)' providing a clear context for who should use it but does not specify when to use versus alternatives or when not to use. No explicit exclusions or comparisons to other tools like browsing the pool.

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