fetch_manager_coaching_rubric

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

With no annotations, the description carries the full disclosure burden, and it does identify the outputs as synthesized guidance rather than stored records, which tells the agent this is a generative/read-style operation. It stops short of stating whether the content is generic or grounded in company policy, whether results are deterministic, or anything about output format.

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?

One front-loaded sentence naming verb, outputs, and inputs, with no filler. It is appropriately sized for a two-parameter tool, though the artifact list could be separated from the input clause for faster scanning.

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 two-parameter tool with a fully documented schema, the description is adequate and usefully names the three output artifacts, which matters since there is no output schema. It is still thin on what the returned structure looks like and whether the agenda is tailored to a meeting length or format.

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% and both parameters carry descriptions plus an enum for performance_rating, so the schema does the heavy lifting. The description echoes the two inputs but adds no extra meaning about how scenario granularity or rating affects the produced guidance — baseline 3.

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?

"Synthesize" is a specific verb and the description names all three artifacts produced (agenda, coaching prompts, feedback guidance) plus the two inputs that shape them, so an agent can tell what it gets back. It does not explicitly contrast with the sibling tools (get_onboarding_milestones, query_hr_policy), but their purposes are distinct enough that the operation is unambiguous.

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?

Usage is implied by the phrase "for a scenario and performance rating" — an agent can infer this belongs in a 1-on-1 preparation flow. There is no explicit statement of when to prefer this over alternatives, no prerequisites, and no exclusion for cases where the rating is unknown.

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