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

Annotations already establish read-only semantics. The description adds a little beyond that by noting the latest profile and compact posts with whole-window counts, but it does not explain pagination, continuation behavior, or output-shape considerations. No contradiction with annotations.

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?

One tight sentence with no filler, front-loading the action and core outputs. It is efficient for what it includes, though slightly too compressed for a tool with 19 parameters.

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 19-parameter tool with no output schema, a one-line description is not complete: it does not specify return layout, how whole-window counts relate to paginated posts, or how to request non-compact output. Schema parameter descriptions help, but 42% of parameters still lack schema documentation and the description does not fill that gap.

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 only 58%, and the description gives almost no parameter-level guidance. Required fields like author_id and date range are not clarified beyond the name, and several schema-undocumented parameters (text, limit, cursor, has_media, post_types, author_ids) remain unexplained.

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 uses a clear verb ('Read') and names specific resources: author identity, latest stored profile, compact posts, and whole-window counts. It does not explicitly contrast with sibling tools like get_posts or search_authors, so it stops short of full differentiation.

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 resource focus on 'author' implies this is the right tool for author-centric reads, but there is no explicit when-to-use guidance or exclusion of alternatives. Given 19 siblings, a sentence on when to prefer this tool over search_authors or get_posts would materially help.

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