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

Annotations already provide readOnlyHint=true and destructiveHint=false, establishing it as a safe, read-only operation. The description adds that it returns 'flags' and is for the current company, but does not delve into behavioral specifics like rate limits or response structure. Given annotation coverage, this is adequate though not extensive.

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 two sentences: the first clearly states the purpose, and the second provides usage guidance. It is front-loaded with the core action and resource, and every sentence adds value.

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 simple, parameterless, read-only tool with good annotations, the description is complete enough. It communicates the purpose and usage intent. The lack of output schema is not critical here, though specifying the flag structure could add minor value.

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 with 100% schema description coverage. Since there are no parameters, the description does not need to add semantics. A baseline score of 4 is appropriate per guidelines.

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 clearly states the action ('get'), the resource ('billing/pricing capability flags'), and the context ('for the current company'). It is specific and distinguishes this tool from siblings, as no other sibling tool deals with billing flags.

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 explicitly advises using this tool before invoking paid-only API behaviors, providing clear when-to-use guidance. While it doesn't mention when not to use it, the context implies it should be used only as a prerequisite check, and no alternative tools are listed.

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