list_report_sign_offs

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

The description adds that it 'returns sign-offs from all users', which is useful context. Annotations already provide readOnlyHint: true, so no contradiction. However, pagination behavior (limit/cursor) is not mentioned.

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: first states the action, second clarifies return content. No unnecessary words, information is front-loaded.

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?

An output schema exists, so return format is covered. The description explains the core behavior adequately. Could mention pagination support given limit/cursor parameters, but overall sufficient.

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 coverage is 100%, so the schema already describes all parameters. The description adds no extra detail beyond the overall purpose, meeting the baseline.

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 sign-offs for a report instance', specifying the verb (list), resource (sign-offs), and context (report instance). The sibling tools include 'create_report_sign_off' and 'get_report_sign_off', so 'list' is distinct and appropriate.

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 implies usage for retrieving all sign-offs but does not explicitly state when to use this tool versus alternatives like 'get_report_sign_off'. No guidance on pagination or when not to use it.

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