Api organisation objectives health 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 structurally. The description contributes nothing beyond that — it doesn't explain what a 'health' payload contains (scores, stale objectives, counts) or whether it requires authentication, which is the only value it could add here.

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?

There is no wasted text, but that is only because there is no text at all. This is under-specification rather than conciseness — a single identifier string carries no front-loaded information for an agent to act on.

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 and no output schema, the description is the only place an agent can learn what this endpoint returns, and it says nothing. For a zero-arg retrieval tool whose whole value is the shape of its response, that leaves a material gap.

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 trivially complete, so the baseline of 4 applies. There are no parameter semantics for the description to clarify or omit.

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 is simply the tool name repeated verbatim ('api_organisation_objectives_health_retrieve'), which is a tautology. It hints at a resource (organisation objectives) and an action (retrieve health) but never states in plain language what 'health' means or what is returned, and provides no differentiation from siblings like organisation_objectives_status_retrieve or organisation_objectives_is_active_retrieve.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. The agent must infer from the name alone whether this supersedes status_retrieve or is_active_retrieve, which it cannot reliably do.

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