Social Get User Info

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

With no annotations, the description must carry behavioral disclosure. 'Fetch' clearly implies a read-only retrieval rather than a mutation, and the schema notes that including comments triggers an extra request. However, auth requirements, rate limits, and side-effect guarantees are not addressed.

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 main description is a single, front-loaded sentence with no filler. It is concise and immediately understandable, though it leaves details such as the comment preview behavior to the schema.

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 simple fetch operation with two fully described parameters and an output schema, the definition is near-adequate. Still, the absence of annotations and the lack of explicit guidance about authentication or when this tool is the right choice create a minor gap.

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 description coverage is 100%, so both parameters are already documented. The description itself adds no parameter-level meaning beyond 'profile,' which is acceptable but not compensating for anything.

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 states a specific verb and resource: 'Fetch a Scratch user's profile.' This clearly identifies the operation and distinguishes it from sibling tools like social_get_project_info and social_get_comments, though 'profile' is not further elaborated.

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?

Usage context is mostly implied rather than explicit. The input schema for recent_comments usefully routes comment pagination to social_get_comments, but the description itself provides no when-to-use guidance or exclusions for alternative profile-related tools.

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