Api organisation objectives is active retrieve

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered and the description cannot contradict it. However, the description adds nothing beyond those structured fields — no indication of what is queried, whether authentication or a specific objective scope is required, or what form the response takes.

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?

It is short with no wasted clauses, but the brevity comes from under-specification rather than economy — the single tokenized phrase conveys nothing front-loadable because there is no real content. Conciseness without information does not earn a high score.

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 carries the full burden of explaining the return value (presumably an active/inactive determination for organisation objectives), and it does not. An agent cannot determine what it will receive or how to use the result.

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, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter-level value could be added here.

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 the tool name verbatim ('api_organisation_objectives_is_active_retrieve'), a tautology that restates the title without stating what the endpoint returns or does. The name hints at organisation objectives and an 'is active' concept, but the description contributes no verb-plus-resource explanation, and the 'is_active' semantics (a boolean flag? a filtered list of active objectives?) remain ambiguous.

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?

There is no guidance whatsoever about when to call this versus the many adjacent siblings such as organisation_objectives_retrieve, organisation_objectives_status_retrieve, or organisation_objectives_health_retrieve. An agent has no basis for choosing this tool over those.

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