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

No annotations provided, so description carries full burden. Fails to disclose error behavior (what happens if user doesn't exist?), rate limits, authentication requirements, or whether the operation is idempotent. 'Find' implies read-only but doesn't confirm safety explicitly.

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, front-loaded with verb and resource. No redundant phrases or structural waste. Appropriate length for a simple single-parameter tool.

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 the simplicity (1 parameter, no nested objects), the description is minimally sufficient but leaves gaps. Without an output schema, it fails to hint at the return structure (JSON object? XML? specific fields like 'firstname', 'lastlogin'?), which would help the agent understand if this meets its information needs.

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?

Schema coverage is 100%, so the parameter is fully documented in structured form. Description mentions 'specific user' which loosely maps to the username parameter but adds no semantic value beyond the schema's explanation. Baseline 3 appropriate when schema does the heavy lifting.

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?

States the resource (BGG user) and general action ('Find'), but uses vague terminology. 'Find' ambiguously suggests search (conflicting with sibling bgg-search) rather than retrieval, and 'details' fails to specify what data is returned (profile, stats, preferences?). Lacks scope specificity.

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 on when to use this versus siblings like bgg-collection (which also returns user-associated data) or bgg-search. No mention of prerequisites like username format or visibility restrictions. The 'SELF' keyword hint exists only in the schema, not the description.

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