pdf_template_config_get

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

Annotations declare readOnlyHint=true and destructiveHint=false, but the description says 'Creates a default config if none exists' — a state-changing side effect. This directly contradicts the read-only annotation. The return-field disclosure is useful, but the contradiction is serious enough to warrant a 1 and an annotation_contradiction flag.

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?

The description is front-loaded with the primary action, then lists return fields, and ends with the default-creation caveat. It is appropriately sized with no filler.

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 tool with a single optional parameter, full schema coverage, and annotations, the description covers purpose and return values. But the side-effect disclosure ('creates a default config') conflicts with the annotation and leaves the agent with an inaccurate behavioral model, and the companyId override is not mentioned in the description.

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 description coverage is 100%, so the single parameter is fully documented in the schema as an optional company UUID that overrides the configured default. The description mentions only 'the current company' and does not add meaning about the override behavior, so it stays at the 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?

The description opens with a specific verb and resource: 'Get the PDF template configuration for the current company.' It also lists the fields returned, making the tool's output recognizable. However, it does not explicitly distinguish this read tool from sibling tools like pdf_template_config_templates or pdf_template_config_preview.

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 implies usage by stating it retrieves the current company's configuration and creates a default if none exists. But it gives no explicit guidance on when to use this tool versus pdf_template_config_templates, pdf_template_config_preview, or pdf_template_config_update.

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