pydantic_section

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

No annotations are provided, so the description must fully disclose behavior. It only says 'extract' without indicating whether it is read-only, if it requires permissions, or what happens on missing anchor. No side effects or limitations are mentioned.

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 a single concise sentence, which is front-loaded. However, it is too terse, sacrificing necessary detail for brevity. Every sentence should earn its place, but here it leaves gaps that reduce overall effectiveness.

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?

Given the tool has an output schema, return values are covered. However, with 2 required parameters and no parameter descriptions, and no usage guidance, the description is incomplete for an agent to understand the tool's full role within the pydantic family.

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%, yet the description adds no explanation for the two parameters. 'path_or_url' could be a file path or URL, but this is not clarified. 'anchor' is left completely undefined. The description fails to compensate for the missing schema descriptions.

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 verb 'Extract', resource 'section', and context 'by anchor from a local page'. It differentiates from sibling tools like pydantic_get (retrieves pages) and pydantic_search (searches). However, the term 'section' is ambiguous—could mean an HTML anchor or a code section—but the anchor parameter clarifies it.

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 guidance on when to use this tool versus alternatives like pydantic_get or pydantic_search. It does not mention prerequisites, when not to use it, or provide examples. The description is purely declarative.

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