post_to_instagram

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

With no annotations, the description must carry the full burden of behavioral disclosure. It lists prerequisites (environment variables, permissions) but does not mention side effects, rate limits, idempotency, or success/failure behavior. For a mutation tool, this is a significant gap.

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 concise and well-structured: a single purpose sentence followed by a clean list of prerequisites. Every word earns its place, with no redundancy or filler.

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?

The tool has only one parameter and no output schema, so the description covers basic usage with prerequisites. However, it lacks parameter semantics and behavioral details, making it adequate only at a minimal level. The presence of a similar sibling tool further underscores the need for more context.

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 description does not mention the content_id parameter at all. The schema defines it as a required string, but the description provides no context on what 'content' refers to or how content_id maps to a resource. With 0% schema description coverage, this is a clear deficiency.

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 uses the specific verb 'post' with a clear resource 'content to Instagram' and mentions the Instagram Graph API as the mechanism. It implies a single-item post, which distinguishes it from the sibling post_carousel_to_instagram, but it does not explicitly state that distinction, so it falls short of a 5.

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 provides prerequisites but no guidance on when to use this tool versus alternatives like post_carousel_to_instagram. There are no explicit 'use this when' instructions or exclusions, leaving the agent without decision criteria.

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