scout_post

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

With no annotations, the description carries full burden. It discloses the login requirement and dry-run behavior for the submit parameter. However, it does not detail error states, post limits, or side effects like irreversible publishes.

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 long with no extraneous words. It front-loads the core action and then adds technical context. Every sentence serves a purpose.

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 description lacks information about the tool's return value or success/failure response. Given no output schema, this is a gap. It also does not connect to other post-management tools, though the context is adequate for the action itself.

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 baseline is 3. The description adds value by specifying that for Medium, the first line becomes the title, and for the submit parameter, it explains the dry-run behavior. This expands on the schema's description.

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 explicitly states 'Compose and publish a post on a social platform (linkedin, x, medium).' This clearly identifies the verb (compose/publish) and resource (post on social platforms), and distinguishes it from sibling tools like scout_delete_post or scout_my_posts.

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 when to use the tool (for posting on specific platforms) but does not explicitly contrast with alternatives or state when not to use it. It mentions automatic handling of platform-specific flows, but no exclusion criteria are provided.

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