persons_list_followers

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

No annotations are provided, so the description takes on full responsibility. It discloses that followers receive notifications and lists output fields, but does not explicitly state that the operation is read-only, nor does it mention permissions, rate limits, or pagination. Adequate but not comprehensive.

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 concise at four sentences, front-loaded with the main action, then detailing output and use cases. Every sentence serves a purpose without redundancy.

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?

Given the simplicity of the tool (one parameter, no output schema), the description covers the essential purpose, output structure, and use cases. However, it could mention whether results are paginated or any other behavioral details, but it is nearly complete for this context.

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 is fully described (100% coverage) for the single parameter 'id'. The description does not add significant meaning beyond the schema's 'Person ID' label, but the baseline is 3 due to high schema coverage.

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 'List all followers of a specific person' with a specific verb and resource. It lists the returned fields and provides use cases, effectively distinguishing from sibling tools like persons_add_follower or persons_delete_follower.

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 includes three explicit use cases, which helps an agent understand when to use the tool. However, it does not mention when not to use it or contrast with similar list-followers tools for other entities (e.g., deals_list_followers), leaving some ambiguity.

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