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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing exactly what the call surfaces (plan, eight strategy sections, current-quarter execution items) and where it originates (/dashboard/oos-operating-plan), which matters given there is no output schema.

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 plus one short usage sentence; the returned content is listed before the sibling reference, and every clause carries information an agent needs. No filler or restatement of the title.

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 output schema, the description carries the burden of describing what comes back, and it does so (plan, sections with content, quarter execution items). Combined with annotations covering the read-only nature and zero parameters, an agent has everything needed to call it correctly.

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 to disambiguate and the baseline is 4. The description correctly spends no words on inputs and instead invests them in describing the returned content.

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 and resource ('Read the organization's active Operating Plan') and immediately enumerates what the read returns: the plan, its eight strategy sections with content, and the current quarter's execution items. That level of specificity also separates it cleanly from write-side siblings like update_operating_plan_section.

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?

Explicitly says to use this before update_operating_plan_section to see what is already there, which gives a concrete sequencing rule with a named alternative. It stops short of stating when-not to use it (e.g., versus browse_oos or get_sections), so it is clear context rather than a full decision table.

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