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

Annotations declare non-readonly, open-world, non-idempotent behavior; the description adds real substance beyond that — the response contains an auth_link the user must open, and Pinterest lacks that link and instead needs a custom application (service_conditions_id). This is valuable flow-level disclosure for an external authorization tool.

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?

Three tight sentences, front-loaded with the core action, then dependencies, then the exception. No filler and every sentence carries information.

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 an output schema present and annotations covering the safety profile, the description does not need to explain return values; it still adds the crucial auth_link and Pinterest caveats. An agent has everything needed to invoke this correctly in-sequence after networks.list.

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 coverage is 100%, so parameter meaning is already fully documented; the description largely repeats it (network_type_id meanings, network_id source). The only genuine addition is tying service_conditions_id to the Pinterest custom-application case, which is marginal beyond what the schema states.

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?

States a specific verb and resource ('Starts authorization for a social network account') and is clearly distinguishable from siblings like connections.list and connections.remove. The scope (an OAuth-style authorization flow) is unambiguous without opening the schema.

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?

Gives clear context: obtain network_id and account type from networks.list before calling, and calls out the Pinterest exception with its special requirement. It does not explicitly say when NOT to use this versus connections.remove/list, but the flow condition is well implied.

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