get_me

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

No annotations provided so description carries burden. States it returns specific fields and implies authentication requirement via 'authenticated Trello user'. Lacks explicit safety/rate-limit notes, but adequate given tool simplicity.

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?

Single sentence, completely front-loaded, no filler words. Every word adds value.

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 tool with output schema, description sufficiently covers purpose and return values. Complete enough for correct invocation.

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?

No parameters (0), baseline 4. Description adds meaning by listing return fields, exceeding minimal expectations.

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?

Description clearly states verb 'get', resource 'authenticated Trello user', and explicitly lists return fields. Distinguishes from sibling tools like get_member which targets specific members.

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?

Implied use for retrieving current user, but no explicit when-to-use or when-not-to-use guidance, nor mentions of alternatives.

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