social_media_posting_get_account

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context—no mention of return format, scope, or any side effects. It purely repeats the getter intent and contributes nothing beyond the structured metadata.

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 one short phrase, but conciseness should not sacrifice informativeness. 'Get Accounts' does not earn its place because it is vague and unhelpful. A longer, more specific description would be better. The structure is minimal but not useful.

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 tool with a single optional parameter and no output schema, the description is severely incomplete. An agent would not understand what is being retrieved, for which platform, or how it relates to other tools. The vagueness makes the tool nearly unusable without external knowledge.

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 provides 100% coverage for the single parameter `locationId`, including its default behavior. The description adds no extra parameter information, so the baseline of 3 applies. The parameter is simple and well-documented in the schema.

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 'Get Accounts' is a verb and resource but extremely vague. It does not specify which accounts (social media? platform-specific?) or distinguish itself from sibling tools like social_media_posting_get_facebook_page_group or social_media_posting_get_posts. An agent cannot reliably tell what this tool does from the description alone.

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 alternative getter tools. There is no mention of context, conditions, or exclusions. The description gives zero assistance in selection.

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