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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds one genuinely useful behavioral point — that the response contains definitions rather than saved organization data — but says nothing about scope per module or how the response differs across modules.

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?

Two compact sentences with the resource area front-loaded and the data-vs-definitions caveat immediately after. There is no filler, though the brevity here edges into under-specification rather than efficient precision.

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?

An output schema exists, so return values need not be spelled out, and the read-only profile is covered by annotations. However, for a schema-introspection tool sitting among many schema-adjacent siblings, the description leaves the key question — what exactly this schema is for and when to prefer it — unanswered.

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 0%, so the description must carry parameter meaning, yet the single required `module` parameter is never mentioned. The phrase "organization app modules" only loosely gestures at it, and the enum values are visible only in the schema with no explanation of how each module changes the returned definition set.

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?

"Inspect create fields for organization app modules" names a resource area but the noun phrase is ambiguous — it is not clear whether it returns a schema of fields used when creating module records, or field definitions themselves. It does not distinguish itself from close siblings such as get_schema, get_module, or get_company_configuration_schema.

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?

No statement of when to call this versus get_schema, get_module, or get_tool_contract, and no prerequisites or exclusions. The agent must infer usage from the tool name alone.

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