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

Annotations already state readOnly=false and destructive=false, so the safety profile is covered. The word "approved" hints at an approval-state precondition and a revision-append model rather than an overwrite, but neither is confirmed, and no side effects or failure modes are described.

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?

A single eight-word sentence with the action front-loaded and no filler. It is efficient, though its brevity tips into under-specification rather than economy.

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?

This is a mutation with no output schema and no annotations covering prerequisites, yet the description says nothing about what state the concept must be in, whether prior revisions are preserved, or what is returned. For a submission tool with an "approved" precondition, that is a real gap.

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 coverage is 100%, so both parameters (concept_id, markdown) are already documented in the schema. The description adds no format, length, or content constraints beyond restating that markdown is markdown, so baseline 3 applies.

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?

"Submit an approved markdown revision for a concept" names a specific verb (submit) and resource (markdown revision on a concept), which is clearer than the adjacent create_concept/update_concept. It stops short of explicitly distinguishing itself from update_concept, so the agent must infer the split.

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 when-to-use guidance is given: nothing says whether this replaces update_concept, whether it must follow list_concept_revisions, or what "approved" gates. The agent has to guess from the sibling list which tool handles concept body edits.

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