me

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether this is a read-only query, any side effects, pagination behavior, authentication requirements, or how results are returned. The example variables show filter/order but no explanation of their effect.

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 brief but the example is a dense JSON blob with placeholders. It front-loads the purpose but the example dominates the text and is not optimally structured for quick scanning.

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 tool with 5 parameters, no output schema, and no annotations, the description only provides an example payload. It doesn't explain the query's purpose, return shape, or context relative to other tools, making it insufficient for an agent to use correctly.

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 example variables clarify the structure of nested 'filter' and 'order' objects, which the schema leaves as generic {}. This adds meaning beyond the schema's bare 'GraphQL: ...' descriptions. However, it omits the 'customer_slug' parameter and doesn't explain each variable's purpose, so it is not a 5.

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 'User · query me' hints at querying the current user, but never explicitly states what the tool does or returns. The variables and example imply a filterable list query rather than a single entity, creating ambiguity. It does not differentiate from sibling tools like 'user' or 'users'.

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?

No guidance is provided on when to use this tool versus alternatives such as 'user' or 'users'. The only hint is 'query me' implying current-user scope, but there are no explicit conditions, prerequisites, or exclusions.

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