group_get

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

No annotations are present, so the description must convey behavioral traits. It labels itself as a 'read endpoint,' implying no side effects, but does not disclose authentication requirements, rate limits, or potential errors. Minimal transparency beyond the operation.

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 sentences, each earning its place: the first defines the function, the second adds valuable context (uniqueness in the SDK). No unnecessary words.

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?

The description covers the tool's core purpose but lacks details on return values, error handling, and the meaning of the boolean parameter. For a simple get-by-ID tool, more is needed given no output schema and no parameter descriptions.

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 description coverage is 0%. The description does not explain the 'groupId' (format or meaning) or 'includeVaultPermissions' (purpose). The sole parameter information comes from the schema, which is unhelpful without descriptions.

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?

Clearly states 'Get one group by ID', combining a specific verb with the resource. The second sentence distinguishes it as the only group read endpoint in the JS SDK beta, setting it apart from sibling 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?

The description implies usage when a group ID is known, but provides no guidance on when to use alternatives or when not to use this tool. Since it's the only group read endpoint, the context is straightforward, but no explicit when-to-use or when-not-to-use is given.

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