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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds important behavior beyond those hints: credits are deducted automatically from recent RankParse calls, the user should not report credits, and client_request_id enables safe retries. It does not discuss permissions, rate limits, or failure behavior.

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?

Three focused sentences front-load the primary action, then add operational constraints. There is no filler; every sentence earns 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?

The core action, credit behavior, and retry mechanism are covered, and no output schema exists to explain. However, with 0% schema description coverage, the description should clarify site_id and kind_hint to be fully complete for an agent invoking the tool.

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 0%, so the description must carry the burden for four parameters. It explains summary as plain text and client_request_id for retry safety, but says nothing about site_id or kind_hint, leaving two of four parameters semantically undocumented.

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 states a specific verb and resource: 'Record what you did for the user in their RankParse activity feed.' It clearly distinguishes this logging tool from the many get_*, list_*, and outreach_* siblings.

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?

It gives clear context for when to use the tool: after doing work for the user, to record it in the activity feed. It also adds a retry-specific guideline ('Pass client_request_id to make retries safe') and a constraint about not reporting credits manually, though it does not name explicit alternatives or exclusions.

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