trello_get_me

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

No annotations, but description accurately describes a simple read operation with no parameters, making behavioral expectations clear. No additional traits needed beyond what is stated.

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 is maximally concise, front-loads the key actions ('Verify', 'return'), and contains no extraneous 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?

Given no parameters, no output schema, and low complexity, the description fully covers the tool's purpose and behavior. No gaps remain.

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 exist; schema coverage is trivially 100%. Baseline of 4 for zero parameters applies, and description adds no extra parameter info (not needed).

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 ('Verify', 'return') and resource ('Trello connection', 'authenticated member profile'), distinguishing it from sibling tools focused on boards, cards, or lists.

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?

Description implies use for verifying connectivity and retrieving profile, but lacks explicit guidance on when to use vs. alternatives. However, as the only tool for the authenticated user, context is clear.

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