get_webportal_config

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

With no annotations provided, the description carries the full burden of behavioral disclosure. However, it offers no information about side effects, read-only nature, data access, or what the tool does besides the noun phrase. It does not even explicitly state that it retrieves configuration.

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 extremely concise, consisting of a single noun phrase. It is front-loaded and free of fluff, but it is under-specified and not a complete sentence, which reduces clarity. It earns a middle score for brevity without waste.

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 no parameters and no output schema, the description is insufficiently informative. It does not state what the configuration contains, what format the return value takes, or how it relates to other configuration tools. An agent would not know what to expect from calling this 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?

The input schema has zero parameters, so the baseline is 4. The description adds a small amount of context by indicating the tool concerns client portal configuration, which aligns with the empty schema. No parameter details are needed.

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 'Configuration du portail client Digital Factory' identifies the resource (client portal configuration) but does not use an explicit verb, relying on the tool name 'get' for the action. It also does not distinguish this tool from other configuration-related siblings like 'get_setup_values' or 'get_company_info'.

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?

There is no guidance on when to use this tool versus alternatives such as 'get_setup_values' or 'configure_*' tools. The description provides no context about the intended use case, prerequisites, or scenarios where this tool is preferred.

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