Api compliance assessments auditee dashboard retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds only the nature of the return (per-assignment progress), and says nothing about scope of data returned, role requirements, or whether results are aggregated across assessments.

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?

A single front-loaded sentence with no filler. It is efficient, though it is so terse that it also carries no routing 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?

With no parameters, no output schema, and permissive annotations, the description should explain the shape of 'per-assignment progress' (which fields, which assignment set, which user's scope) since nothing else does. It conveys only the gist, which is minimal but workable for a simple read endpoint.

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 tool takes zero parameters and the schema is fully described, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies.

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?

Concrete verb (returns) plus a specific resource (per-assignment progress data) scoped to the auditee dashboard, so the agent knows the kind of payload produced. It does not, however, distinguish itself from close siblings such as compliance_assessments_is_auditee_retrieve, recap_retrieve, or progress_ts_retrieve, which also surface compliance-assessment progress views.

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 phrase 'for the auditee's dashboard' implies the scenario (auditee-role dashboard views) but never states when to call this versus the many other compliance-assessment progress/recap/status endpoints. No prerequisites (e.g., auditee role) or exclusions are given, leaving selection to inference.

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