Get Groups

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

Annotations only declare readOnlyHint=true. The description adds useful behavior beyond that: list mode omits long-form fields, private groups are visible only with subscribed_only, and group_id returns the complete record. It does not discuss auth requirements, rate limits, or pagination, but those are less critical for a read-only tool with an output schema.

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?

Three sentences, front-loaded with the core action. The group definition and create_share pointer support correct usage, and the final sentence concisely explains the two invocation modes. No filler.

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 read-only tool with two optional parameters, 100% schema coverage, and an output schema, the description supplies the needed context: what the tool does, the two modes, the privacy behavior of subscribed_only, and the cross-tool share workflow. Nothing essential is missing.

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 the schema already documents both parameters and the baseline is 3. The description adds nuance by clarifying that private groups the user joined appear only when subscribed_only is set, and that group_id returns one group's complete record. These details go slightly beyond the schema's wording.

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 Fulcra groups, or get one group's full details.' It also explains the group concept and points to create_share for sharing, which helps differentiate from share-related siblings, but it does not explicitly name list_shares or state when to choose this over other group tools.

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?

Describes when to pass group_id (for one group's complete record) and when to set subscribed_only (private joined groups appear only then). It also mentions create_share as the alternative for sharing with all group members. However, it does not state any when-not conditions or exclusions for other listing tools.

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