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

Annotations declare readOnlyHint=true, so the description does not need to emphasize that. The description adds context about what the output contains (profile IDs, platform, handle) and its prerequisite role. It does not disclose potential nuances like whether it includes all accounts or only those eligible for posting, but with readOnlyHint, the bar is lower and this is adequate.

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, front-loaded with the core purpose and ending with explicit guidance to call it before scheduling. Every sentence earns its place, zero 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?

The tool is simple with no parameters and a readOnlyHint annotation. The description tells the agent what it returns and when to use it. Without an output schema, it could benefit from explaining what 'posting targets' are exactly (e.g., social media profiles) but the description does this. It is complete enough for its purpose.

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?

There are 0 parameters, so the schema provides no parameter information. The baseline for 0 parameters is 4, and the description does not need to add parameter semantics. It does explain the output (profile IDs, platform, handle), which is useful.

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 what the tool does: it lists posting targets (profile IDs) with platform and handle, needed for targeting a post. It explicitly names the resource (posting targets) and the purpose (provide profile IDs for targeting), distinguishing it from sibling tools like sprkly_list_connected_social_accounts.

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 clearly states when to use this tool: 'Call this before sprkly_schedule_post.' However, it does not explicitly say when not to use it or mention alternatives (like sprkly_list_connected_social_accounts), though its specific purpose implies it for scheduling.

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