Account/group description

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

Annotations already declare readOnlyHint=true, covering the safe-read aspect. The description adds useful context about group targeting and optional column selection, but does not disclose behavior for missing accounts, invalid columns, or the exact return format. No contradiction with annotations.

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?

The description is two sentences, front-loaded with the core purpose and containing only essential usage details (group targeting and optional column). No filler or redundancy.

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 the low complexity (3 parameters, no output schema), the description covers the core function, group targeting, and optional column return. It could optionally mention return format or error behavior, but the schema and annotations cover the parameters and read-only nature, making this adequate.

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 100%, so the baseline is 3. The schema already documents all parameters, including the 'Gr=1' syntax and the column XML name. The description does not add any parameter semantics beyond what is in the schema.

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 starts with 'Return the description of an account or group', a specific verb+object pair. It also explains the 'Gr=<id>' syntax for targeting groups and mentions the optional column feature, making it clearly distinct from sibling tools such as banana_accounts or banana_cell.

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 gives clear context that this tool is for retrieving descriptions, and it provides a specific usage guideline with the 'Gr=<id>' selector. It does not explicitly list alternative tools or exclusions, but the context is sufficiently clear for when to use this tool.

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