user_current

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds the contextual detail that the user is the webhook's acting identity. It does not disclose return format or additional behavior, but given the read-only annotation, the description's contribution is modest yet non-contradictory.

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, short sentence that is efficiently front-loaded with the core purpose. It is concise and contains no filler, though it could be slightly more explicit with a verb phrase.

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 zero-parameter, read-only tool with an output schema (as indicated), the description is sufficient. It clarifies the operational context (webhook) and the return value. The output schema presumably details the return structure, so the description does not need to elaborate further.

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 and 100% schema coverage, the description does not need to elaborate on parameters. The baseline for no-parameter tools is 4, and the description appropriately avoids redundant parameter information.

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 the tool returns the user on whose behalf the webhook operates, which clearly identifies the resource and purpose. It is a noun phrase rather than a verb+resource construction, but the meaning is unambiguous and distinct from siblings, as no other tool references the current user.

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 description implies usage when the agent needs to know the executing user of a webhook, but does not explicitly state when to use it versus alternatives or provide exclusions. There are no similar sibling tools, so context is implied rather than explicit.

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