get_group_honor_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It uses the verb 'Get', which implies a read, but it does not state whether the operation is read-only, requires special permissions, has no side effects, or how results are shaped. The description is too thin to satisfy the transparency burden.

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 short, but it is under-specified rather than properly concise: it simply restates the tool name in natural language. The single sentence does not earn its place because it contributes no useful information beyond the name.

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 parameter schema is complete enough to invoke the tool correctly with group_id, and optional type values are listed. However, there is no output schema, no behavioral context, and no explanation of what 'honor information' actually returns, so the description is only minimally sufficient.

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 schema description coverage is 100%, with both group_id and type already documented in the input schema. The description adds no parameter-level meaning, but this is acceptable because the schema already defines the type values and the required group_id.

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 'Get group honor information' is essentially a word-for-word expansion of the tool name get_group_honor_info, so it adds no new information beyond restating the identifier. It identifies a resource but does not specify what 'honor information' includes or how it differs from other group-related 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?

There is no guidance about when to use this tool versus alternative tools such as get_group_info, get_group_info_ex, or get_group_member_list. The chosen behavior must be inferred entirely from the tool name and parameter schema, which is insufficient for robust agent selection.

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