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

Annotations provide readOnlyHint=false and idempotentHint=true, but the description adds critical behavioral context beyond that: report_instructions is prepended to EVERY member's and the orchestrator's prompt on every run, empty strings clear fields, and saves are checked against a prompt-injection deny-list and secret scan (rejected on a hit). It also states authorization constraints and explicitly lists what it does NOT change. No contradiction with annotations.

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?

Every sentence earns its place: the main purpose, the key side effect of report_instructions, the usage pattern, exclusions, authorization constraints, and a pointer to the discovery tool. It is front-loaded with the primary action and keeps all additions relevant. No fluff or repetition.

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?

The description is complete for a tool with a full 4-parameter schema and an output schema. It covers scope, permissions, side effects, exclusions, and related tool guidance. The only thing not explained is the return value, but the output schema presumably handles that. Nothing an agent needs to select and invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by clarifying the partial-update pattern ('pass... only the fields you want to change'), the clearing behavior for empty strings, and the strategic role of report_instructions as a team-wide behavioral lever. These semantics are not fully covered by the schema's parameter descriptions, though the schema is already quite detailed.

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 states a specific verb and resource: 'Edit the settings of YOUR OWN department — its reporting instructions, name, and description.' It enumerates the exact fields and clarifies what it does not do ('does NOT change the department's composition'), which distinguishes it from sibling tools like findagent_edit_metadata and the web builder. An agent can immediately identify this tool's unique scope.

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 description gives explicit when/when-not guidance: 'Owner-only, personal departments only (an org department is edited from the org workspace)' and 'composition... edited in the department builder on the web.' It also tells the agent to call findagent_list_my_agents to discover owned departments, and describes the partial-update pattern ('pass only the fields you want to change'). No ambiguity remains about when to use this tool.

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