pinterest_get_me

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

There are no annotations and the description reveals no behavioral details such as side effects, required permissions, or return format. It is completely silent on what happens when the tool is called.

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 extremely short but is not a well-formed sentence and lacks a verb. It sacrifices clarity for brevity, so it does not effectively earn 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?

With no parameters or output schema, the description is the only source of information. It fails to explain what the tool does or what it returns, leaving the agent completely in the dark about the tool's function.

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 has zero parameters and the schema coverage is 100%, so the baseline of 4 applies. No parameter descriptions are needed because there are no parameters to explain.

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?

Description is a noun phrase ('The authenticated Pinterest account.') with no verb, so it does not clearly state what the tool does. It fails to distinguish this tool from siblings like pinterest_list_boards or pinterest_get_pin_analytics.

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 on when to use this tool versus the many sibling tools. The description offers no context about its intended use case.

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