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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: the result is a single aggregate JSON object and it includes sensitive sections such as claims, grants and the audit log. It does not disclose response size, whether the audit log is truncated, or any permission requirements.

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 colon-led sentence with the scope stated first and the payload contents enumerated after it. No filler, no restatement of the title, and nothing that could be cut without losing information.

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 aggregate with no output schema, the enumerated contents largely stand in for a return-value description, which is the key thing an agent needs. Minor gaps remain around payload size, truncation behavior, and whether the audit log is complete or windowed.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly avoids inventing filtering options that the schema does not support.

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 pairs a specific verb ("Return everything") with a specific resource (owner data) and enumerates the entity types returned: party, offerings, needs, matches, interactions, claims, grants and audit log. That enumeration implicitly separates it from narrower siblings like get_details and get_inbox. It stops short of naming an alternative outright, so it is clear but not fully sibling-differentiated.

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 explicit statement of when to call this versus get_details, get_inbox, or search, nor any mention of prerequisites or exclusions. The only usage signal is implicit in "everything," which an agent must infer means a full-scope export rather than a targeted read.

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