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

Annotations already mark readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the auth requirement and the exact data categories returned, which goes beyond what the annotations provide; no rate-limit or failure behavior is disclosed, but that is not critical for this simple read-only tool.

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?

A single sentence packs all essential facts with no filler: the data returned and the auth requirement. It is front-loaded with the functional payload and remains easy to scan for an agent.

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 parameterless, read-only self-profile tool, the description is complete: it identifies whose data is returned, which fields are included, and the required authorization. The absence of an output schema is acceptable because the description explicitly enumerates the returned information.

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?

With zero parameters, the schema already trivially covers parameter semantics, and the description correctly adds no parameter details. The 0-parameter baseline of 4 applies, and there is no gap to compensate for.

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 immediately identifies the resource as 'my network standing' and enumerates the specific facts returned: publisher status, payable login, trailing-7-day points, payout status, and payout history. It clearly implies a read-only self-status query, though it lacks an explicit action verb and does not itself distinguish it from adnet_stats or adnet_report.

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 text says what the tool returns and that it requires an Authorization header, which signals it is intended for the authenticated user. It does not explicitly state when to choose this tool over adnet_stats/adnet_report or other alternatives, leaving usage to be inferred rather than stated.

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