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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description's contribution beyond that is the ownership requirement, which is genuine but thin — nothing about behavior when no policy exists or what the application status represents.

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 short sentences, zero waste, with the resource and scope front-loaded before the permission qualifier. Nothing could be removed without losing 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 read-only tool whose safety profile is carried by annotations and which returns the policy plus its status, this is minimally sufficient. It omits edge cases (no policy configured, insufficient permissions beyond 'owners only') and the shape of the returned status, though the absence of an output schema makes that less critical.

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 0% and the single parameter (organizationId, a UUID) is never mentioned in the description, so the description does not compensate for the coverage gap. The parameter is near self-explanatory from its name and format, but the description adds nothing.

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?

States a specific verb ('Read') and resource ('Team sync policy') plus the extra dimension of 'application status', which cleanly separates it from the sibling reads like get_team. However it does not explicitly distinguish itself from preview_team_sync_policy or publish_team_sync_policy, so the sibling differentiation is left to inference.

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?

Adds a real usage constraint ('Team owners only'), which tells the agent who may call it, but gives no guidance on when to prefer this over preview_team_sync_policy or publish_team_sync_policy, nor any preconditions such as requiring an existing policy.

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