get_pinterest_user

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

Without annotations, the description must cover behavioral traits. It only states the action without disclosing that it requires authentication, is read-only, or what constitutes 'account info'. No details on potential errors or side effects.

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 a single concise sentence, efficiently conveying the core purpose. However, it could be expanded slightly to include parameter or behavioral info without losing conciseness.

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 output schema and minimal schema info, the description is incomplete. It omits what data the tool returns, authentication requirements, and any error handling context. A more detailed description would improve agent usability.

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 has one parameter (access_token) with 0% description coverage. The description does not mention the access_token or its role, leaving the agent without guidance on whether it's optional or required, or how to obtain it.

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 specifies the verb 'Get' and the resource 'authenticated Pinterest user account info', making the tool's purpose immediately obvious. It distinguishes well from sibling tools like get_pinterest_board or search_pinterest_pins.

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?

There is no explicit guidance on when to use this tool versus alternatives. However, among the many siblings, none duplicate this specific function, so the usage context is implied. A user would infer this is for the current authenticated user only.

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