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

Annotations declare readOnlyHint=true, so the safety profile is covered. The description adds useful context beyond that: the active-member filter, the exclusion of unaccepted invitations, and the shape of returned data (description, fields, members, belongs_to, you). It doesn't discuss pagination or rate limits, but for a read-only list operation this is solid added value.

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 core purpose is front-loaded, but the single dense sentence enumerating returned fields (description, fields, members, belongs_to, you) is hard to parse and front-loads detail that could be secondary. It's information-dense but not efficiently structured.

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 compensates by explaining the returned data structure and the resource concept. It covers scope, definition, and return shape. Missing only pagination/ordering behavior for a list operation, which is a minor gap.

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 with 100% schema coverage means the baseline is 4 per the rubric. The description details the structure of what's returned rather than input parameters, which is appropriate and provides helpful expectation-setting since no output schema exists.

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 and resource ('List the AccountHub shared projects you belong to') and defines the resource precisely in a later sentence. It goes further by explicitly stating what a shared project is NOT ('it is NOT a Slack workspace and has nothing to do with list_accounts'), which is strong differentiation from a 70+ tool sibling set that includes both Slack tools and list_accounts.

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?

Clear context and scope boundaries: 'Only projects where you are an active member are listed; invitations you have not accepted on the web are not shown.' It also points to update_shared_project for the belongs_to field. However, it doesn't say when to prefer alternatives like list_shared_items or list_shared_activity for related queries.

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