find_user_by_username_fetch_profile_info_fetch_user_post_2

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

No annotations are provided, so the description carries the full burden. It hints at a multi-step process ('does a sequence of actions under the hood') but doesn't disclose what those actions are, what data is returned, or any behavioral traits like error handling or performance. This leaves the agent with minimal insight into how the tool behaves.

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 incomplete and poorly structured, ending abruptly mid-sentence. It fails to convey essential information efficiently. While it's brief, this is due to under-specification rather than effective conciseness, making it unhelpful for the agent.

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 tool's name suggests complexity (finding user by username, fetching profile info, and fetching user posts), the description is severely incomplete. With no annotations, no output schema, and a truncated description, it fails to provide enough context for the agent to understand what the tool does or returns, making it inadequate for use.

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 schema description coverage is 100%, with the single parameter 'X-Fields' documented as 'An optional fields mask'. The description adds no information about parameters, as it's cut off before mentioning any. With high schema coverage and no parameter details in the description, the baseline score of 3 is appropriate.

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 starts to explain what the tool does ('finds user by...') but is incomplete and cut off mid-sentence. It mentions a sequence of actions but doesn't specify the full purpose. This is more than a tautology but remains vague and unfinished, failing to clearly state the complete tool purpose.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions. Given the sibling tools include similar user-finding tools (e.g., 'find_user_by_sec_user_id_fetch_profile_info_fetch_user_p'), the lack of differentiation is a significant gap.

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