favorite_contributor_network_item

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

With no annotations provided, the description adds key behavioral traits: idempotency (safe to repeat) and scope 'contributor-network.write' (authorization needed). This is sufficient for a simple mutation tool.

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?

Two concise sentences, front-loaded with purpose and idempotency, then scope. No wasted words.

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?

The description covers the core action and idempotency but lacks parameter explanation. For a simple tool with no output schema, this is adequate but not fully complete.

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 description coverage is 0%. The description does not explain what 'item_id' refers to. For a single parameter, clarifying that it is the ID of the contributor network item would add value.

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 'Set the caller's favorite flag for an item (idempotent).' It uses a specific verb and resource, and distinguishes from the sibling 'unfavorite_contributor_network_item'.

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 explicit guidance on when to use this tool versus alternatives like 'unfavorite_contributor_network_item'. The description only provides permission scope, not usage context.

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