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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered externally. The description adds nothing beyond that – it does not say what 'status' values exist, what an unknown/missing actor returns, or whether the persona must already exist.

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 single sentence is front-loaded and free of filler, but at this length it is under-specified rather than truly concise; there is no structural content to speak of.

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 one-parameter lookup tool with no output schema, annotations, or sibling routing, the description is too thin: it never defines the returned status concept or distinguishes itself from persona_list or the work-status tools.

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 single actor_id parameter has no property-level description (0% schema coverage), and the description does not explain what actor_id is, whether it is optional, or what happens if it is omitted. The description fails to compensate for the schema gap.

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 names a verb (查询) and a resource (Persona 状态), so the basic action is identifiable. However it gives no differentiation from siblings like persona_list, get_work_status, or batch_get_work_status, leaving the agent to guess which status-retrieval tool applies.

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 indication of when to call this versus persona_list or the other status/query tools, and no prerequisites or exclusions are stated. Usage must be inferred entirely from the name.

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