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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no mutation warning is needed. The description adds context beyond annotations by specifying that only public updates are returned and that the result order is simply what the server returns, which prevents agents from assuming a guaranteed sort.

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 with no filler. The resource and purpose appear first, the clarifying definition of 'twits' is compact, and the second sentence justifies practical use without repeating schema information.

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 paginated list operation, the description, combined with the fully documented input schema and read-only annotations, gives an agent everything needed to call it correctly. The lack of an output schema is not a gap because the returned resource is clearly identified as a team's list of twit posts.

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 page, page_size, and team_id are already fully described in the input schema. The description adds no extra parameter-level meaning, which matches the baseline expected when the schema carries the documentation burden.

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 opens with the specific verb 'List' and a concrete resource: a team's public updates ('twits'), which are defined as short build-log posts. This clearly distinguishes team_posts from sibling getters such as team_get or team_members, which concern team metadata rather than the team's update feed.

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 gives explicit use cases: catching up on a team's activity and checking what has already been posted before writing another update. It also points to team_post as the write counterpart, providing an alternative, although it does not enumerate broader when-not-to-use exclusions or other sibling read tools.

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