get_new_following_7d

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

No annotations provided, so description alone must disclose behavior. It reveals a 7-day window and 'crypto ecosystem' filter but omits return format, pagination, rate limits, authentication needs, or what happens if no new follows exist. Insufficient for safe invocation.

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?

Single sentence, 12 words, front-loaded with purpose. Efficient but could incorporate brief usage guidance without excessive bloat.

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?

No output schema, no annotations, and moderate complexity (3 params, time filter). Description lacks return format, crypto filter definition, and parameter requirements. Incomplete for agent decision-making.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning to parameters beyond what the schema provides. Remains adequate but unhelpful.

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 tool retrieves accounts followed in the last 7 days, distinguishing it from 'get_following' (all follows) and 'get_new_followers_7d' (followers). However, 'crypto ecosystem' is ambiguous—does it filter to crypto-related accounts or imply the user is in crypto? This slight vagueness prevents 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?

No guidance on when to use this tool versus siblings like 'get_following' or 'get_new_followers_7d'. No prerequisites mentioned (though schema implies one identifier required). No exclusions or when-not-to-use.

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