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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds substantial beyond-that context: meaning of valuePreview, externalIsCanonical, requiresAppActivation, phoneVerification, and the canOneClick=false/no-externalUrl blocking rule, plus the agreement-display requirement. The field shorthand is cryptic and mostly concerns the submit workflow, but the behavioral disclosure is well above the annotation baseline.

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 text is a single run-on block of semicolon-separated shorthand clauses with no front-loaded statement of what the tool does. Much of the content (fill rules, agreement display, attachment handling) belongs to the submit workflow rather than this read tool, so length is not fully earned here.

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?

With no output schema, one parameter, and a read-only profile, the description goes further than required by naming the key fields a caller will encounter (viewer, status, missingRequired, valuePreview) and the constraints governing them. It is close to complete for the read step, though the jargony field names are never defined.

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?

There is a single parameter with 100% schema description coverage, and the schema already documents slug and its origin from list_signup_feed items[].slug. The description adds nothing about the parameter, so the baseline 3 for fully-covered schemas applies.

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 title names a specific resource ('a signup detail for one activity, including my registration status'), and the first clause implies the tool returns viewer current value/status/missingRequired. However, the body is dominated by procedural fill-in rules rather than stating plainly what the tool returns, so an agent must infer the core purpose from snippets. It is distinguishable from get_signup_gaps only because that sibling is named incidentally.

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?

Explicit routing is present: '多场get_signup_gaps' names the alternative and its condition, '已报勿重复' gives a when-not rule, and normal vs sensitive attachments route to prepare_signup_file_upload or the App. It stops short of 5 because the guidance is tangled with field-semantics and submission rules rather than cleanly framed as when/when-not for this read tool.

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