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

With no annotations provided, the description must carry the full behavioral burden. It states the operation is a read-only 'get' that returns a list with descriptions, but it does not disclose error behavior, rate limits, or any potential side effects. For a simple list tool this is minimal, and the agent is left to infer that it is safe.

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 a single, clear sentence with no redundancy. It front-loads the action and resource, making it easy to understand at a glance.

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?

For a simple list tool with one parameter and no output schema, the description sufficiently covers what it returns (a list of frameworks with descriptions) and the required context (a specific social media network). It could be more explicit about output structure or completeness, but given the low complexity, it is largely complete.

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 input schema has 100% coverage for the single 'network' parameter, including a list of valid values. The description adds general context about network-specific listing but does not contribute meaning beyond the schema's property description, so a baseline 3 is appropriate.

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 action ('Get a list'), the resource ('available copywriting frameworks'), and the scope ('for a specific social media network'). It distinguishes itself from the sibling 'get-copywriting-framework' which implies retrieving a single framework.

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 this tool (when you need all frameworks for a given network) but does not explicitly contrast it with 'get-copywriting-framework' or mention when not to use it. There are no explicit alternatives or exclusions, so the guidance is implied rather than direct.

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