delimit_social_accounts

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

With no annotations, the description fully discloses behavior: read-only side effect, underlying call (ai.social.list_twitter_accounts), and file scanning pattern (~/.delimit/secrets/twitter-<handle>.json). This goes beyond typical transparency.

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?

Description is concise yet comprehensive, using clear sections (purpose, usage, sibling contrast, side effects, args, returns). Every sentence adds value with no redundancy.

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 0 parameters and an output schema (implied by mentioning return structure), the description is fully complete. It explains the tool's role, side effects, and return format without gaps.

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?

Tool has no parameters (empty schema, schema coverage 100%). Description explicitly states 'Args: None', which is sufficient. Baseline for 0 params is 4, and the added context about internal calls earns a 5.

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?

Description clearly states the tool lists configured social media accounts (Twitter/X) and distinguishes from sibling tools delimit_social_generate (drafting) and delimit_social_post (publishing). The verb 'list' and resource 'configured social media accounts' are specific and unambiguous.

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?

Explicitly provides when to use (inventory accounts before drafting/posting) and when NOT to use (draft or publish). Names specific alternatives (delimit_social_generate, delimit_social_post) for incorrect use cases.

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