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

Annotations already cover safety (readOnly, idempotent, non-destructive) and openness. The description adds genuinely new context: the data is read through the user's saved WIP login (external credential dependency), 'Posts nothing', and 'Pro' hints at plan gating. The terse 'Pro.' fragment is unexplained, and nothing is said about failure behavior when the login is missing or expired.

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 lead sentence is a dense run-on that chains two result sets together, and the trailing 'Pro.' is an unexplained fragment. Information is front-loaded and nothing is wasted, but restructuring into two or three short sentences would make the routing and return shape much easier to parse.

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?

With no output schema, the description carries the return-value burden and does so: hashtags per WIP project, the AimYear project/lever each maps to, and the unmatched AimYear projects/levers. Combined with annotations that cover safety, an agent has what it needs to call this correctly; only the meaning of 'Pro' remains unclear.

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?

Zero parameters, so the schema imposes no documentation burden; baseline 4 applies. The description adds no parameter detail because none exists, and correctly spends its words on what the tool returns instead.

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?

States a specific verb+resource: listing the user's own wip.co projects with hashtags, plus the AimYear projects/levers that lack a hashtag. The scope ('user's own', read via saved WIP login) is explicit. It is slightly convoluted by the dual result set, but an agent can tell this apart from the set_* siblings it names.

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?

Gives a clear precondition ('once WIP is connected') and names the follow-on tools (set_projects / set_levers, wip_hashtag) plus an escalation rule ('asking the user only when unsure'). It lacks an explicit when-not-to-use case, but the workflow context is clear enough to act on.

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