list_visibilities

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It only states that it lists values, but does not mention that it is read-only, non-destructive, or any side effects. Authentication requirements (optional token) are implied but not stated in the description.

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 two sentences: the first states the core action with examples, the second provides usage guidance. It is front-loaded, concise, and every sentence is valuable with no waste.

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 no annotations, the description does not specify the return format (e.g., array of strings) or error conditions. It is minimally adequate for a simple list tool but lacks some context that would help an agent fully understand the tool's behavior.

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% with the accessToken parameter already described. The description does not add any meaning beyond the schema; it focuses on the purpose. Baseline of 3 is appropriate as no extra value is added.

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 the verb 'list' and the resource 'valid post visibility values' with examples (PUBLIC, CONNECTIONS). It distinguishes itself from siblings like create_post by showing how the output is used, and whoami is unrelated.

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?

The description implies use when needing valid visibility values for create_post. It does not explicitly exclude other uses, but the context with siblings is clear. No explicit when-not-to-use is given, but it's sufficient for a simple reference tool.

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