group_get

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

With no annotations, the description carries the full burden. It does disclose one genuinely useful behavioral trait: the payload contains member handles with 'no ids/PII', telling the agent the result is privacy-safe to surface. It says nothing about permissions, behavior on an unknown/unauthorized id, or whether the result is cached/limited.

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?

One short sentence, so there is no bloat, but the leading '[KEEP · internal]' tag is curation metadata that consumes the most prominent position without helping an agent decide or invoke. The useful content is not front-loaded.

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 getter with no output schema, describing the returned entity (topic, member handles, shared cards) is the right kind of content and is partially complete. Missing: what the id identifies, error/empty behavior, and any access constraints — the same gaps the absent annotations would otherwise have covered.

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?

The single required 'id' parameter has 0% schema description coverage and the description adds nothing about it — it never says what kind of id is expected (group id vs. member handle vs. slug) or its format. The 'no ids/PII' note refers to the response, not the input parameter.

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 never states a verb; it only characterizes the payload ('A study group: topic, member handles, and shared-study cards'). From the name group_get an agent can infer retrieval, but it is not differentiated from siblings like groups_list or group_contribute, so the purpose is only implied.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. membership), and no routing to alternatives such as groups_list for enumeration. The agent must infer that this fetches a single group by id.

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