whodb_platform_shared_by_me

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety and repeatability are covered. The description adds that the workspace target does not change defaults, which is useful behavioral context, but it says nothing about output shape, pagination, or scoping of team_id when omitted.

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 short sentences, zero filler, and the core purpose is front-loaded before the workspace note. Nothing is padded or repeated.

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?

Given zero required parameters, an annotated read-only list tool, and full schema coverage, the description is adequate but not rich: it omits any routing to the many sibling list tools (shared_with_me, org_resources, user_owned_resources) that an agent would need to pick correctly among.

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 coverage is 100%, so all five parameters including the nested workspace object are already documented in the schema, including the default-resolution chain (session_use, then process/saved defaults). The description adds only a short restatement of workspace targeting, so the baseline 3 is appropriate.

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 (List) and resource (resources shared by the signed-in user), and the phrase 'by the signed-in user' distinguishes it from siblings like whodb_platform_shared_with_me and whodb_platform_user_owned_resources. It does not name those siblings explicitly, so the differentiation is implied rather than stated, keeping it just under a 5.

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 explains what the workspace param does for per-call targeting but never says when to prefer this tool over whodb_platform_shared_with_me, whodb_platform_org_resources, or whodb_platform_user_owned_resources. Usage is implied by the name but no explicit when/when-not guidance is given.

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