get_my_posts

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

The annotations declare readOnlyHint=true, but the description explicitly discloses a state-changing side effect: appending a metrics snapshot to a local file. This directly contradicts the annotation, so the behavioral transparency score must be minimal.

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?

Two sentences, both necessary: the first states the core return value, the second flags an important side effect. No filler or redundant schema repetition.

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 covers the basic purpose and the side effect, and an output schema exists. However, the readOnly contradiction and lack of parameter semantics leave an agent uncertain about invocation details, especially what account=null means and how limit behaves.

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 0%, and the description does not explain the limit or account parameters. The word 'account's' weakly ties the account parameter to the posts returned, but limit remains entirely unexplained and account=null is not clarified.

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 states a specific resource ('The account's recent posts') and lists the returned metrics (score, comments, upvote ratio, age). It is clear and distinguishable from the sibling list by name, though it does not explicitly name an alternative.

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 explicit when-to-use guidance or exclusions are provided. The side-effect note hints at a relationship with timing tools, but the description does not tell the agent when to choose this over get_post_timing_data, get_post_details, or get_account_stats.

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