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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false; the description adds genuinely new context beyond them: the creator-only permission gate on visibility and the clarification that visibility is workspace-internal and never public. It does not explain what data gets destroyed or that body fields can be nulled/cleared, which is the main residual gap.

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?

Purpose is front-loaded, followed by parameter notes and behavioral caveats, with no filler sentences. The parenthetical parameter summary is dense but efficient.

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 mutation tool with an output schema present and annotations covering safety/idempotency, the description covers permission and visibility scope well. It is only slightly short on clarifying that omitted vs null fields behave differently, which matters for a partial-update tool.

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?

With schema coverage at 0% and a nested body object, the description does meaningful work by noting body holds "the create fields, all optional" and that id is a uuid, implying a partial update. However none of the ten nested fields (city, name, tags, visibility, etc.) receive any semantic explanation in either schema or description.

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?

"Update program metadata" states a specific verb and resource, and "metadata" implicitly distinguishes it from sibling mutators on sub-entities like update_program_item and update_program_info_card. It does not name any sibling explicitly, so the differentiation is inferable rather than stated.

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 one concrete condition (visibility changes require CREATOR) but no explicit when-to-use/when-not guidance relative to the many update_* siblings. Usage is implied by "program metadata" rather than articulated.

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