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

Annotations already establish this is a safe read (readOnlyHint true, destructiveHint false, openWorldHint false). The description adds genuinely non-obvious behavior: results are paginated to one page with a nextCursor, and there is no entry quota. It does not explain what includeContent changes or the shape of returned items, keeping it below 5.

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, front-loaded with the action and followed by pagination behavior. Nothing is padded, though the second sentence is a weak generic nudge rather than substantive content.

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 four undocumented parameters, no output schema, and a vague notion of what 'published context' contains, the description leaves significant gaps. An agent cannot tell what includeContent does or how query is matched, which matters for calling this correctly.

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 0% and none of the four parameters (query, cursor, memberId, includeContent) are explained in the description. 'memberId' is only obliquely referenced via 'a public member's context,' and the semantics of query and includeContent — arguably the most ambiguous inputs — are entirely undocumented.

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 gives a specific verb and resource: 'Search a public member's published context.' An agent knows it is a search over one member's content. It does not distinguish itself from siblings like get_person_card or assess_profile_context, and 'context' remains loosely defined, so it falls short of 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 closing line 'Retrieve relevant context before reasoning' implies a usage moment — fetching background prior to answering. However, no alternative is named and no exclusion condition is given, so the routing guidance against six sibling tools is left to inference.

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