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

Annotations are all false, providing no useful safety or effect hints. The description compensates by disclosing the toggle behavior (state changes) and that follows are public social signal, which is meaningful context. It doesn't mention permissions or side effects like notifications, but the toggle nature is clearly communicated.

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 sentences, front-loaded with the core action and toggle behavior. Every word adds value, with no redundancy or filler. The structure is highly efficient for the agent to quickly grasp the tool's purpose.

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 one-parameter toggle tool, the description covers the main behavior and social impact. However, it omits any explanation of the 'handle' parameter, which is critical for invocation. The schema is minimal and output schema absent, so the description should have addressed the parameter to be complete. It's 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%, and the description does not mention the 'handle' parameter at all. It fails to explain what the handle refers to (e.g., the node identifier) or provide any guidance on its format or source. The schema only gives a field name with no description, so the description should compensate but does not.

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 tool follows or unfollows a node on the mesh, explicitly noting it toggles. The verb 'follow/unfollow' and resource 'node' are specific, and the toggle behavior distinguishes it from sibling tools like mesh_subscribe or mesh_refer.

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 gives clear context: use this to toggle follow status on a node. It doesn't explicitly mention alternatives or exclusions, but the toggle semantics and public nature imply when it's appropriate. No other tool in the sibling list offers the same follow/unfollow behavior, so the context is sufficient.

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