twitter_get_profile

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

The description indicates it returns a JSON string with specific fields and implies authentication ('authenticated user'), but with no annotations, it does not explicitly disclose read-only behavior, error conditions, or rate limits. The 'Fetch' verb suggests a safe read operation, but this is not explicit.

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 concise, containing only two sentences that clearly state the purpose and return data, with no unnecessary information. It is front-loaded and every sentence earns its place.

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 tool with an output schema, the description adequately specifies the return format and scope. It clearly states that it fetches the authenticated user's profile and lists key fields returned. No additional context is necessary for such a simple, self-contained operation.

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 tool accepts zero parameters, and the schema coverage is 100% by default. The description adds no parameter details, which is appropriate given there are no parameters to document, aligning with the baseline of 4 for zero-parameter tools.

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 clearly states a specific verb ('Fetch') and resource ('the authenticated user's Twitter/X profile information'), distinguishing it from sibling tools like threads_get_profile by specifying the platform and the authenticated user's own profile. The scope is unambiguous.

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 is provided regarding when to use this tool versus alternatives. It does not mention exclusions, alternatives, or specific contexts, leaving the agent to infer usage solely from the name and description.

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