weixin_get_config

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

No annotations are provided, so the description must cover behavior. It discloses that the config includes the typing_ticket needed for sendTyping, which is useful. However, it does not state whether the operation is read-only, whether authentication is required, or how errors are handled, leaving some gaps.

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 a single, front-loaded sentence with no filler. It states the action, the key output element, and the recommended call timing, each earning its place.

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 simple config getter with two parameters and no output schema, the description adequately conveys the primary purpose and the important typing_ticket field. It lacks detail on the full return structure or failure modes, but the tool's complexity is low, so a 4 is appropriate.

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 schema already documents user_id and context_token. The description mentions 'user' and 'typing_ticket' but does not add semantic detail beyond the schema, so it stays at the baseline of 3.

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 clearly states 'Get bot config for a user' with a specific verb and resource, and singles out the typing_ticket purpose. This distinguishes it from sibling tools like weixin_send or weixin_contacts, which handle different operations.

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 phrase 'Call before sending typing indicators' provides explicit timing and context for when the tool should be invoked. It does not mention when not to use it or alternative tools, but the usage context is clear, making it a 4 rather than a 5.

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